[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=c...
]
Sam Douglass commented on HHH-3486:
-----------------------------------
How are Maven users are completely unaffected? Since the Hibernate pom.xml doesn't
specify dependencies on any specific adapters you can't actually use Hibernate by just
adding a dependency on it to your project's pom.xml. You are required to additionally
add a dependency on a specific SLF4J adapter to your project's pom.xml file. It's
a bit like a missing dependency. The Hibernate pom.xml should specify a default adapter
(e.g. the JDK adapter) to include so that just adding a dependency on Hibernate provides a
working version of the API. Then people can optionally depend on a different adapter in
their project's pom.xml file if they like.
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