On Tue, Nov 27, 2012 at 2:36 AM, Justin Edelson <[email protected]> wrote: > ...WDYT about a much simpler structure where: > 1) On startup, a config file in a location relative to sling.home is > consulted. If it does not exist, some default configuration is used....
I like that - being able to configure logging right from bootstrap time is very useful for troubleshooting startup/upgrade problems. > 2) Once a resource resolver factory is located, the configuration file is > reloaded from a configurable location... ok - I'd prefer avoiding XML if we can, but I don't know how flexible logback is. IMO it would be nice to make this change as non-disruptive as possible for Sling "administrators", so: a) Keep the OSGi console configuration and the same basic principles for logging (maybe with different configuration fields and values) b) Convert existing logger configurations at startup -Bertrand
