[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:
---------------------------------
SLF4J could easily default to an NOP implementation if no binding
artifact were found. However, this has the disadvantage of leaving the
user scratching her head wondering why no logging output is
generated. With SLF4J's current fail-fast approach, an error message
is displayed followed by and exception, the user adds the desired
binding artifact on the class path and the issue is solved for good.
It ain't perfect but it works.
You are welcome to create an SLF4J bug report at
http://bugzilla.slf4j.org. Continuing here is OK as far as I am
concerned.
Include one ore more SLF4J "adapters"
-------------------------------------
Key: HHH-3486
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486
Project: Hibernate Core
Issue Type: Improvement
Components: build
Affects Versions: 3.3.0.GA, 3.3.0.SP1, 3.3.1
Reporter: Chris Bredesen
Assignee: Steve Ebersole
Hibernate, as of 3.3, no longer distributes all jars needed to run the framework. 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. Maven users are
of course unaffected since the additional SLF4J jars are published in the central repo.
"Adapter" may be the wrong term here but I think the point has been made :)
--
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