http://bugzilla.slf4j.org/show_bug.cgi?id=138 josh@kivasystems.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josh@kivasystems.com --- Comment #21 from josh@kivasystems.com 2011-05-26 06:15:18 CEST --- We have exactly this problem, however we are not using Weblogic, we have a custom framework. In our case the problem appears to be because each of our project jar files list the same slf4j binder in their own manifest class path. Although the actual -classpath parameter we pass to the JVM lists the binder only once, each of our jars list the binder in their manifest. SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/home/path-to-app/lib/slf4j-log4j12-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/path-to-app/lib/slf4j-log4j12-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/home/path-to-app/lib/slf4j-log4j12-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. We are using Maven as our build system and it is creating the manifest automatically. I'm sure we could tweak the dependencies in our build system to work through this, but using a Set does seem like the semantically correct thing to do in this situation anyway. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.