| commit | 05c38023de2778e96feeb8255d52a2d8101f5695 | [log] [tgz] |
|---|---|---|
| author | Chetan Mehrotra <chetanm@apache.org> | Mon Feb 10 12:43:32 2014 +0000 |
| committer | Chetan Mehrotra <chetanm@apache.org> | Mon Feb 10 12:43:32 2014 +0000 |
| tree | 052a4069be8c5053a1acb8066ef3ee5e5a243b01 | |
| parent | 36292512c0afa022c5f31dcb598f5a4d33afc441 [diff] |
SLING-3045 - [logback]Warning logs logged for 'No appenders present in context [sling] for logger' Instead of removing the console logger asscoaited with root logger by default we check now if root logger has any appender associated with it or not. if not then console logger is not removed Also moved this logic out as a separate listener and ensure that this listener is invoked at the end of config cycle. git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1566597 13f79535-47bb-0310-9956-ffa450edef68
The “log” project packages the Logback library to manage logging in OSGi environment. It provide some useful extension to the default Logback feature set to enable better integration with OSGi. The SLF4j API bundle must be installed along with this bundle to provide full SLF4J logging support.
The Logging bundle should be installed as one of the first modules in the OSGi framework and - provided the framework supports start levels - be set to start at start level 1. This ensures the Logging bundle is loaded as early as possible thus providing services to the framework and preparing logging.
For more details refer to the Logging Documentation
You can compile and package the jar using the following command:
mvn package -Pide,coverage
It would build the module and also produce a test coverage report also prepare bundle jar which is suitable to be used to run integration test from within IDE.