[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: --------------------------------- I was trying to point out that the current situation is not as bad as described by Chris Bredesen when he writes: SLF4J requires the inclusion of the SLF4J library as well as either a native or a wrapped implementation. The manual vaguely references such a need but it's never quite clear that the user must visit the SLF4J website and obtain these jars himself. When the user hits the problem of the missing slf4j-binding, he or she is warned by SLF4J with a reference for further information. This runtime warning is more than "a vague reference in the manual". It should also be quite clear from the reading the description of the error code that the user must download a binding from the SLF4J site. If for some reason the message emitted by SLF4J or the description of the error code is unclear, I suggest that these be improved instead of hard-coding an slf4j binding in hibernate. As you say, the choice of the logging framework should be made by the end-user. I welcome your suggestions in regard to the message emitted by SLF4J as well as the related error description in [1]. [1] http://www.slf4j.org/codes.html#StaticLoggerBinder -- 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