[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=c...
]
Steve Ebersole commented on HHH-3486:
-------------------------------------
Ceki, I think what you say is fine. Are you making a suggestion that I am missing?
We currently use 1.5.8. TBH I have not tested the theory about simply logging a warning
versus throwing errors. I know back when I was first pointed to slf4j it was the case
that y'all actually threw errors if the binding was not found. If that is really no
longer the case and y'all simply log a warning message, then this is perfect imo (this
is really no different than shipping log4j and not including a log4j.properties). So, if
this is the case, issue closed 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