我也犯了同样的错误。我已经在我的本地开发中配置了slf4j-api, slf4j-log4j12和log4j。所有配置都很好，但是我从mvnrepository复制的slf4j-log4j12依赖项有测试范围<范围>测试</范围>。当我把这一切都是好的。

有时愚蠢的错误会让我们崩溃;)

我也遇到过类似的问题，通过以下方法解决了问题:

文件->项目结构… 模块->依赖项 从Maven ->搜索:slf4j.nop 单击最新版本-> Apply

当我得到以下错误时，我陷入了这个问题:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

当我在我的库中使用slf4j-api-1.7.5.jar。

尽管我尝试了整个建议的补充jar，如slf4j-log4j12-1.7.5.jar, slf4j-simple-1.7.5，但错误消息仍然存在。当我将slf4j-jdk14-1.7.5.jar添加到java库中时，这个问题最终得到了解决。

在http://www.slf4j.org/download.html上获得整个slf4j包

他们的官网给出了解决方案:

Failed to load class org.slf4j.impl.StaticLoggerBinder This warning message is reported when the org.slf4j.impl.StaticLoggerBinder class could not be loaded into memory. This happens when no appropriate SLF4J binding could be found on the class path. Placing one (and only one) of slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem. SINCE 1.6.0 As of SLF4J version 1.6, in the absence of a binding, SLF4J will default to a no-operation (NOP) logger implementation. If you are responsible for packaging an application and do not care about logging, then placing slf4j-nop.jar on the class path of your application will get rid of this warning message. Note that embedded components such as libraries or frameworks should not declare a dependency on any SLF4J binding but only depend on slf4j-api. When a library declares a compile-time dependency on a SLF4J binding, it imposes that binding on the end-user, thus negating SLF4J's purpose.

解决方案:我已经添加到我的项目中使用intellij的maven研究，我选择了slf4j-jdk14.jar。

我也犯了同样的错误。我已经在我的本地开发中配置了slf4j-api, slf4j-log4j12和log4j。所有配置都很好，但是我从mvnrepository复制的slf4j-log4j12依赖项有测试范围<范围>测试</范围>。当我把这一切都是好的。

有时愚蠢的错误会让我们崩溃;)

简单地添加到你的pom.xml:

<dependency>
  <groupId>org.slf4j</groupId>
  <artifactId>slf4j-simple</artifactId>
  <version>1.7.21</version>
</dependency>