Is Log4j a dead project? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

I recently ended up in a bit of a mess on 开发者_如何学Pythonone 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?

---

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.