I reproduced a similar issue, and (as requested by Ceki on the mailing list) attached an archive with the test project. Unpack this archive, run "mvn clean install t7:run" and you will get:
java.lang.ClassCircularityError: org/slf4j/helpers/NOPLogger
at org.slf4j.helpers.SubstituteLoggerFactory.getLogger(SubstituteLoggerFactory.java:53)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:270)
at org.slf4j.bridge.SLF4JBridgeHandler.getSLF4JLogger(SLF4JBridgeHandler.java:204)
at org.slf4j.bridge.SLF4JBridgeHandler.publish(SLF4JBridgeHandler.java:289)
at java.util.logging.Logger.log(Logger.java:458)
at java.util.logging.Logger.doLog(Logger.java:480)
at java.util.logging.Logger.logp(Logger.java:596)
at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:183)
at org.apache.juli.logging.DirectJDKLog.debug(DirectJDKLog.java:106)
at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:368)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
at org.apache.catalina.startup.Catalina.start(Catalina.java:675)

The bridge listener is the only listener in the project, so reordering the listeners does not help me. Moving the LevelChangePropagator in logback.xml from the beginning to the end of the file, as suggested on http://stackoverflow.com/a/11798287, does help.
Logback is latest (1.0.7), SLF4J is latest (1.0.7), tried with different JDKs (1.6.0_21, 1.7.0_07).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev

Reply via email to