Logback

Logback was meant to be the successor of the Log4j logging framework, now an Apache project.

The entire framework was designed to be generic, so developers can easily adapt and embed it in their projects.

The Logback project is actually made of 3 parts:

logback-core

logback-classic

logback-access

Each of them plays its one part and allows developers to use them in various ways with other present day technologies.

What is new in this release:

• Logback now supports an unlimited level of variable resolution graphs rather than being limited to one level deep resolution.

What is new in version 1.1.3:

• Logback now supports an unlimited level of variable resolution graphs rather than being limited to one level deep resolution.

What is new in version 1.0.13:

• In logback-access MANIFEST file, imports of Jetty and Tomcat are now optional.

What is new in version 1.0.12:

• The code detecting whether Groovy is available on the class path deals with the case where logback binaries are installed as endorsed libraries.
• Logback is now able to retrieve the name of localhost when running under OS X and Java 7.
• DBAppender in logback-classic module no longer assumes that caller information is always available.
• In order to simplify our build, several unit tests have been ported from Scala to Java. It follows that logback no longer depends on Scala, not even during the test phase of the build.

What is new in version 1.0.11:

• The "cn" conversion word now correctly maps to ContextNameConverter class.
• Added gray to the list of ANSI colors supported by logback.

What is new in version 1.0.7:

• Groovy dependency upgraded to version 2.0.0.
• Janino library upgraded to version 2.6.1.
• The code handling variable substitution has been completely re-written.
• The color-related conversion words now set the default color correctly.
• Substitution properties are now correctly recognized by scan and scanPeriod attributes of <configuration> element in configuration files.
• Fixed a race-condition in AsyncAppender and its worker thread.
• If a PropertyDefiner implements LifeCycle, then its start() method will now be invoked.

Requirements:

• Groovy 2 or higher