tomcat 启动显示日志级别，以及SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".错误

把以前的一个老项目通过maven的方式搭了一下，tomcat启动时，打印信息特别多，当时判断日志显示级别应该是debug.但我配置与之前没有任何改变，所以问题应该出在pom.xml上，于是网上查找资料，发现还真有类似的情况，于是效仿解决之。
我们的日志是用log4j
处理方法：

<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-classicartifactId>
<version>${logback.version}version>
<type>jartype>
<scope>compilescope>
dependency>
<dependency>
<groupId>ch.qos.logbackgroupId>
<artifactId>logback-coreartifactId>
<version>${logback.version}version>
<type>jartype>
<scope>compilescope>
dependency>

去掉这两个jar.
去掉之后，果然没有过多信息了，但又出了这个问题：

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.

于是去他提供的网址查看，

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.

于是就在maven中心库下了个与slf4j版本对应的slf4j-nop.jar问题得以解决。