On Wed, May 11, 2011 at 17:46, coldserenity <[email protected]> wrote: > 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
Anyway in this case all you have to do is remove from xwiki so that it use the one provided by JBoss which make sense anyway. > > Regards, > Roman > > -- > View this message in context: > http://xwiki.475771.n2.nabble.com/Proposal-Switch-from-Commons-Logging-Log4j-to-SLF4J-Logback-tp6343910p6352403.html > Sent from the XWiki- Dev mailing list archive at Nabble.com. > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
