On Tue, Apr 5, 2011 at 1:21 PM, Christian Grobmeier <grobme...@gmail.com> wrote:
> No releases, no question, no discussion on commons-logging. > Lack of development on Log4J > Slf4J has a rising community and active development. > > commons-logging imho is the wrapper for a slowly dying log4j and a not > usable sdk log. Whenever I find myself forced to using slf4j (mostly, because some damned application library forces me to), then it is inevitablly slf4j-log4j. In other words, I am simply using slf4j in exactly the manner you describe: As yet another wrapper over log4j. And why is that? Because log4j is the very, very successful de-facto standard for logging and every application server I have used in the last 10 years (notable exception: Tomcat, which for some unknown reason ships jul logging, but not slf4j) ships with Log4j built in. Thanks god, they do. The only purpose of slf4j seems to be to cause unneeded fragmentation and discussions like this, Christian, which you are stirring now for the nth time (n > 5, for sure). Jochen -- I Am What I Am And That's All What I Yam (Popeye) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
