Logback is intended as a successor to the popular log4j project, and was designed by log4j's founder, Ceki Gulcu. The basic architecture is sufficiently generic so as to apply under different circumstances. It is divided into three modules. The Core module lays the groundwork for the other two modules, whereas the Classic module can be assimilated to an improved version of log4j. It natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging systems, such as log4j or JDK14 Logging. The Access module integrates with Servlet containers to provide HTTP access log functionality. You can easily build your own modules on top of the Core module.
|Tags||Logging Software Development Libraries Java Libraries|
|Operating Systems||OS Independent|
Release Notes: This release fixes several bugs.
Release Notes: This release has bugfixes and small enhancements, but nothing earth shattering.
Release Notes: A number of cool new features were added in this release, most notably encoders and graceful recovery from IO failures.
Release Notes: This version is mainly a maintenance release that corrects several bugs.
Release Notes: This release fixes the methods isInfoEnabled, isWarnEnabled, and isErrorEnabled in the ch.qos.logback.classic.Logger class, which previously failed to work correctly. The various Logger.isXYZEnabled(Marker) methods now take into account the marker information passed as parameters. As discussed in bug 54, during automatic initialization, it makes better sense to first check for the logback-test.xml file, and only if that fails to check for logback.xml.