Any reason for a new project to use log4j instead of Logback? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 8 years ago.

Improve this question

I know that the common opinion is that Lo开发者_Python百科gback > log4j. Still, is there anything log4j does better than Logback? Any reason to use log4j over logback? How about the fact it only has 60 questions on stack overflow, so I presume a much smaller user base?

---

Take a look at official opinion. log4j isn't under active development anymore, and since logback is being developed ground up by the same author as log4j, Ceki Gülcü, to correct some mistakes made in log4j's development, you can be pretty sure that using logback isn't a bad idea.

---

No matter what logging backend you choose, I suggest using slf4j as a frontend to it. It may seem like overkill, but in these times of dependency injection and abstraction, having a simple layer between you and the logging impl isn't so crazy.

As noted by Ceki, Logback's public API actually is slf4j, so if you choose Logback and use it in the recommended way, you are already using slf4j.