I recently ended up in a bit of a mess on one of the projects I work on, a "mélange" of Log4j, Slf4j and Commons-Logging due to mixing different JARs from different open source projects.
I see more and more OS projects slowly moving to Slf4j. Logback seems to be the successor of Log4j. I think it's actually a fork, but since no further development are anticipated for Log4j 1.3 and Log4j 2.0 is an experimental development and don't know if it will ever leave that state... I wonder!!!
Is Log4j dead?
The Apache Log4j Project is among the most deployed pieces of open source software, providing logging capabilities for Java applications. Log4j is part of the Apache Logging Services Project -- an open source effort within the Apache Software Foundation.
log4j is a tool to help the programmer output log statements to a variety of output targets. In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4j it is possible to enable logging at runtime without modifying the application binary.
Apache Log4j is a Java-based logging utility originally written by Ceki Gülcü. It is part of the Apache Logging Services, a project of the Apache Software Foundation. Log4j is one of several Java logging frameworks.
No.
Mature, complete, stable - none of these are synonyms for "dead".
Deprecated, superceded - perhaps this is what you meant? Is Log4j superceded by Slf4j? Given that Slf4j implements a wrapper for Log4j... probably not. It's just an alternative way to use Log4j.
Log4j is robust, stable, widely accepted and in production use across the globe.
Logback is intended to be a successor for Log4j but has not yet had equivalent exposure. Slf4j allows you to abstract out the logging framework.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With