commit | 00460c2e8c92fe029e917ff6023863228ea6911c | [log] [tgz] |
---|---|---|
author | Chetan Mehrotra <chetanm@apache.org> | Wed Jul 22 05:03:34 2015 +0000 |
committer | Chetan Mehrotra <chetanm@apache.org> | Wed Jul 22 05:03:34 2015 +0000 |
tree | 607b9b3727441baa853d601c43be8864cb41af39 | |
parent | cc3192365403d341fb4293c7a510341ce8d0e8fd [diff] |
SLING-4840 - Provide an option to disable a set of logger via config LogConfig now supports resetToDefault mode which is mapped to log level of DEFAULT. If enabled then logger state would be set to default i.e. no explicit log level set, additive to true and no appender explaicitly attached git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1692218 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.