logback: a worthy successor to log4j?

As you may have already heard, I have been working on a new project
called logback, intended as a worthy successor of log4j.

On the 5th of December, I'll will be presenting (in French) the top 10
reasons for migrating your projects to logback. Issues such as
migration strategy, new APIs, SLF4J and Joran will be
discussed. Emphasis will be given to practical aspects and a live demo
rather than relatively theoretical considerations.This free-entry
event is organized by Hortis.

For those who may not be able to attend my presentation, here is abrief summary:

• Logback is an improved version of log4j
• Given that logback is built on top of SLF4J, you can switch to a another logging system at will.
• The new Joran configration API sits at the core of logback.
• The Status API for accrued resilliance. Logback's status API enables internal error reporting in a simple yet powerful way without adding complexity.
• Documentation: already good and getting better by the day.
• Filtering API. If you can imagine it, logback can filter it.
• Marker objets to color log statements for highly-specialized processing.
• Access module: easy integration with access logs generated by Tomcat or Jetty
• JMX: You can configure logback at runtime using Mbeans.
• TDD: logback has been developped test first. Moreover, logback is available for use, today.

The full presentation is also available. Anyway, I hope you will be able to attend.