Two slf4j implementations on the classpath #16
Labels
Milestone
Comments
jonashackt
added a commit
that referenced
this issue
Sep 13, 2017
…r, because that leads to interferences with Spring Boot´s logback logging (see https://stackoverflow.com/questions/30792268/loggerfactory-is-not-a-logback-loggercontext-but-logback-is-on-the-classpath) and the warnings with every run of your cxf-spring-boot-starter dependend application. This is now fixed.
|
Problem was a dependency of mojo-executor. |
jonashackt
added a commit
to codecentric/cxf-spring-boot-starter
that referenced
this issue
Sep 13, 2017
…er-maven-plugin (codecentric/cxf-spring-boot-starter-maven-plugin#16) now provides only one slf4j implementor, so no errors like "LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation" should occur any more. Also the downgrade of logback isn´t necessary any more.
jonathangarcia414
added a commit
to jonathangarcia414/spring-boot-starter
that referenced
this issue
Nov 8, 2022
…er-maven-plugin (codecentric/cxf-spring-boot-starter-maven-plugin#16) now provides only one slf4j implementor, so no errors like "LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation" should occur any more. Also the downgrade of logback isn´t necessary any more.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When starting an app, there are some warnings from slf4j that if found more than one implementor, which will lead to an Spring Boot Application start error containing
LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementationfrom classorg/springframework/boot/logging/logback/LogbackLoggingSystem.class.The text was updated successfully, but these errors were encountered: