[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-3486) Include one ore more SLF4J "adapters"

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=c... ] Ceki Gulcu commented on HHH-3486: --------------------------------- Sam's comments are two pronged. Let me answer each in turn. If only slf4j-api.jar is not found on the classpath but no binding artifact such as slf4j-simple.jar or slf4j-log4j12.jar, then LoggerFactory will output an error message (mentioned multiple times above) and throw an exception. This is indeed different than log4j.jar without log4j.properties which would simply output a warning message without failing (whereas SLF4J fails). On Sam's 2nd point. Adding more flexibility in SLF4J's binding strategy (via properties) would introduce an unnecessary level of complexity. Having said that, if you place 2 or more bindings on the class path, SLL4J will pick up the first, and output a warning message listing the location of all the bindings, i.e. jar files, it found, so that you can remove the superfluous bindings. SLF4J will not fail in this case. HTH -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira