[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=c...
]
Steve Ebersole commented on HHH-3486:
-------------------------------------
Ceki, I think the confusing part in your first comment is that its not *just* outputting a
warning message. "Warning" implies "you might want to change this".
No, it throws exceptions and then outputs a message to the effect you said.
I must say that on the surface I completely agree that it seems very odd that having no
"logging binding" on the classpath causes the entire application to fail to
load. I agree that I don't think it makes sense to use different names for the
binders. That is sort of against the whole idea here. But like I said, making that
condition an error seems over the top. Especially for frameworks; it sort of of leaves us
in a bind.
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