控制台报如下错误:
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.

我的问题是在测试log4j2的时候，始终无法打印日志，先是找到了下面的官网，然而我的是log4j2,如果像下面那样处理的话，就无法实现log4j2，后来去本地仓库查看jar包，发现本地关于log4j2的Jar全是lastUpdate，私服上并没有log4j2的包。

查看第三条的网址，官网解答如下：

image

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.

控制台打印这个信息的时候，需要添加slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar中的一个(只需要添加任意一个)。这是针对log4j实现的时候的解决方案。