今天在修改项目是修改了pom中的配置启动后提示下面的错误,
1 SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". 2 SLF4J: Defaulting to no-operation (NOP) logger implementation 3 SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
而且日志内容也不再显示。
查看网址的内容解决方法
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.
翻译过来就是：
这个错误是当org.slf4j.impl报道。StaticLoggerBinder类不能被加载到内存中。发生这种情况时,无法找到合适的SLF4J绑定类路径。slf4j-nop放置一个(且只有一个)。slf4j-simple jar。slf4j-log4j12 jar。slf4j-jdk14 jar。jar或logback-classic。jar的类路径应该解决这个问题。
解决方法就是添加下面的依赖：
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-access</artifactId>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
</dependency>
也测试了加入
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
</dependency>
但是日志的显示效果不是自己想要的，springboot推荐的是logback.xml来管理日志,而且我在项目中添加了对应的logback_spring.xml文件