Hi all I just noted a problem in the way the logging infrastructure is configured currently with Sling Commons Log 5.0.
I have a use case, where I have the global configuration provided as properties in sling.properties. This configuration is log file name, log format pattern, and log file rotation setup. When starting up the system I see logging going to stdout until way after the system has started. Tracking this down I see that the initial (re)configuration of the logging system happens *asynchronously* triggered by the call to the configChanged() method in the LogbackManager constructor. Wouldn’t it be possible to have the initial (re)configuration done synchronously from the LogbackManager constructor such that when Sling Commons Log is fully started (activator terminated) the logging is configured at least according to the framework properties (which is where the sling.properties are injected) ? Thanks Felix
