Hi All, In sonar-core, looking at the Logback class in the org.sonar.core.config package, you can find following lines:
import ch.qos.logback.classic.LoggerContext; import org.slf4j.LoggerFactory; ... LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); Sonar is assuming that SLF4J is bound with Logback, not an unreasonable assumption for stand-alone Sonar or for a maven-plugin before Maven started using SLF4J. However, with Maven 3.1, this assumption proves to be incorrect. I would suggest to contact Sonar people so that the code which configures Logback first checks that SLF4J is bound to Logback. If not, the code should not attempt to configure logback. Basically, Sonar should add a few lines of defensive code. My 2c. -- Ceki 65% of statistics are made up on the spot --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org