通过Leif's Hypoport post的启发，这是怎么了我“弯曲”休眠4回SLF4J：
让你使用Maven承担。
- 作为依赖添加
org.slf4j:log4j-over-slf4j您pom.xml
- 使用命令
mvn dependency:tree，确保没有你使用上slf4j:slf4j depende文物的（准确地说，没有神器应有编译范围依赖或上slf4j:slf4j运行时范围依赖性）
背景：休眠4。 x对神器org.jboss.logging:jboss-logging有依赖性。在传递上，这个神器具有提供的范围依赖于神器slf4j:slf4j。
正如我们现在已经添加了org.slf4j:log4j-over-slf4j神器，org.slf4j:log4j-over-slf4j模仿了slf4j:slf4j神器。因此，所有JBoss Logging日志现在实际上将通过slf4j。
假设您使用Logback作为您的日志记录后端。下面是一个简单pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
....
<properties>
....
<slf4j-api-version>1.7.2</slf4j-api-version>
<log4j-over-slf4j-version>1.7.2</log4j-over-slf4j-version>
<jcl-over-slf4j-version>1.7.2</jcl-over-slf4j-version> <!-- no problem to have yet another slf4j bridge -->
<logback-core-version>1.0.7</logback-core-version>
<logback-classic-version>1.0.7</logback-classic-version>
<hibernate-entitymanager-version>4.1.7.Final</hibernate-entitymanager-version> <!-- our logging problem child -->
</properties>
<dependencies>
<!-- begin: logging-related artifacts .... -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<version>${slf4j-api-version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>jcl-over-slf4j</artifactId>
<version>${jcl-over-slf4j-version}</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>log4j-over-slf4j</artifactId>
<version>${log4j-over-slf4j-version}</version>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-core</artifactId>
<version>${logback-core-version}</version>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
<version>${logback-classic-version}</version>
</dependency>
<!-- end: logging-related artifacts .... -->
<!-- begin: some artifact with direct dependency on log4j:log4j .... -->
<dependency>
<groupId>org.foo</groupId>
<artifactId>some-artifact-with-compile-or-runtime-scope-dependency-on-log4j:log4j</artifactId>
<version>${bla}</version>
<exclusions>
<exclusion>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- begin: some artifact with direct dependency on log4j:log4j .... -->
<!-- begin: a hibernate 4.x problem child........... -->
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>${hibernate-entitymanager-version}</version>
</dependencies>
<!-- end: a hibernate 4.x problem child........... -->
....
</project>
在classpath中，有logback.xml，比如这一个位于src/main/java：
<!-- begin: logback.xml -->
<configuration>
<appender name="console" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
</encoder>
</appender>
<logger name="org.hibernate" level="debug"/>
<root level="info">
<appender-ref ref="console"/>
</root>
</configuration>
<!-- end: logback.xml -->
有些部件可能希望在JVM启动时间访问logback.xml用于正确的日志记录，例如Jetty Maven插件。在这种情况下，请将Java系统logback.configurationFile=./path/to/logback.xml添加到您的命令中（例如mvn -Dlogback.configurationFile=./target/classes/logback.xml jetty:run）。
如果你仍然得到“原始”控制台stdout Hibernate输出（如Hibernate: select ...），那么堆栈溢出问题“Turn off hibernate logging to console”可能适用。
+1突出显示日志记录Hibernate的文档已经过时 – mhnagaoka 2013-10-29 17:48:14