My problem is extremely similar to the one outlined in this post (it is unanswered): Is SLF4jJ 1.8.0-alpha2 compatible with Log4j 2.8.2.
I am trying to upgrade from slf4j 1.7.36 to 2.0.0-alpha7.
Currently I have this in my POM:
<!-- https://logging.apache.org/log4j/2.x/maven-artifacts.html -->
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
<version>2.17.2</version>
</dependency>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
<version>2.17.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/org.slf4j/slf4j-api -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>1.7.36</version>
</dependency>
<!-- https://logging.apache.org/log4j/2.x/maven-artifacts.html -->
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
<version>2
.17.2
This works as intended.
Every time that I try to change slf4j to 2.0.0-alpha7 I get the following error:
SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#noProviders for further details. SLF4J: Class path contains SLF4J bindings targeting slf4j-api versions prior to 1.8.
Does anyone know what causes this?