| commit | fee867522b07931bc2a0c00d10d01700a27a6cbe | [log] [tgz] |
|---|---|---|
| author | Chetan Mehrotra <chetanm@apache.org> | Fri Jul 24 11:41:32 2015 +0000 |
| committer | Chetan Mehrotra <chetanm@apache.org> | Fri Jul 24 11:41:32 2015 +0000 |
| tree | a6c66716588f9e5231e2b1a7ce8f0da282d2c573 | |
| parent | 16902d7016944ab25e86f8d8530cf45d1d8d4772 [diff] |
SLING-4788 - SlingConfigurationPrinter should use mode aware and only stream the full logs in the zip version and avoid duplicate information Added support for restricting number of old rolled over log files to be included in the configuration status dump. By default max 3 files would be included. This can be configured via 'org.apache.sling.commons.log.maxOldFileCountInDump' config prop git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1692482 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.