This is a great idea and a very nice patch. Thanks! However I do have a few comments.
1) indeed the line length formatting needs to be fixed, 80 char max (some wiggle room but generally 80 is max)
2) the default should be log and exit for 3.5. not exiting is really a bug, and since it's configurable I think it's fine to be b/w compatible when it comes to the new release. (so you'd have two patches that are slightly different, that's ok). I would mark this jira as "incompatible" and add a release note to this jira for inclusion in the release notes of the effected releases
3) this is a bigger comment. You shouldn't be using constants to mark "logonly" "logandexit" etc.... Rather you should be configuring which class to handle the strategy.
a) Define an interface for this strategy
b) Implement three default classes to be available for use in the config file. (log/logexit/none)
c) document this (intf and concrete classes) in the guide
the nice thing about this approach is say that someone comes along and needs a fourth option. Say it's osgi specific, or "page me", etc... They can implement their own class and then just specify that strategy in the config file. It will be much more adaptable going forward.