+1 Thanks, Marius On 05/09/2011 02:37 PM, Vincent Massol wrote: for the following reasons: leaks under some circumstances). http://www.google.fr/search?aq=f&sourceid=chrome&ie=UTF-8&q=slf… > * logback is the successor of log4j and addresses the following when compared to lgog4j: > http://logback.qos.ch/reasonsToSwitch.html > * New stuff happens in logback and not in log4j > * I'd also like to switch to logback since it has full-fledged JMX support which allows us to easily change logging configuration at runtime (changing log levels for example): > http://logback.qos.ch/manual/jmxConfig.html > Note that migrating a log4j.properties file is easy: http://logback.qos.ch/translator/ > In addition if a user wants to stay on log4j it would be possible and easy: simply remove the logback jar and replace it with the slf4j-log4j one. > WDYT? > Thanks > -Vincent > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

There's one issue with slf4j to be aware of. As you probably know slf4j does not allow several versions of slf4j (APIs and implementations) to be located in the classpath. This applies for e.g. JBoss 5.1. It internally uses older version of slf4j. By default in JBoss 5.1 applications do not have isolated classpath. This results in JBoss slf4j being loaded first and potentially conflicting with your app's slf4j may you try to deploy (especially for newer versions of slf4j). This may not be a critical issue (in our case things worked, but we've isolated our web application's classpath and yet the warning got printed), but worth double-checking. Check this post for the details of the issue http://community.jboss.org/thread/157454

Regards,  Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/Proposal-Switch-from-Commons-Logging-Log4… Sent from the XWiki- Dev mailing list archive at Nabble.com. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Thomas Mortagne wrote: Agree. Unless slf4j API used in XWiki is new enough to be incompatible with the one in JBoss 5.1 (implementation for which, by the way, is a custom one - it contains 2 additional JBoss classes with unknown purpose and removal impact). I guess it's rather the issue with JBoss (which is promised to be fixed in either v6 or v7). Just something to be aware of. ( Sorry for disturbing the vote process :) )