Is Log4j a dead project?

I recently got in a mess in one of the projects I'm working on, "mélange" Log4j, Slf4j and Commons-Logging due to mixing different JAR files from different open source projects.

I see that more and more OS projects are slowly moving to Slf4j. Login seems to be the successor to Log4j. I think that this is actually a plug, but since further development is not expected for Log4j 1.3 and Log4j 2.0, and Log4j 2.0 is an experimental development and I do not know if it will ever be able to leave this state ... Interesting !!!

Is Log4j dead?

+4
source share
1 answer

No.

Mature, full, stable - none of them are synonyms for the "dead".

Fatigue, curtailed - perhaps this is what you had in mind? Is Log4j replaced by Slf4j? Given that Slf4j implements a wrapper for Log4j ... maybe not. This is just an alternative way to use Log4j.

Log4j is reliable, stable, widespread and used in production all over the world.

Logback is designed for the successor to Log4j, but so far has no equivalent exposure. Slf4j allows you to abstract from the logging structure.

+10
source

All Articles