[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486?page=c...
]
Chris Bredesen commented on HHH-3486:
-------------------------------------
Again, this issue was about shipping a complete distribution, not about behavior. Steve
you were quite adamant in the past about shipping at least one working connection pool
with Hibernate so that the end user would have a more complete distribution. Indeed,
looking in the beta 2 archive, I see both c3p0 and Proxool. Given that, I assumed that
these optional-but-required SLF4J adapters would surely make the cut. Shipping a jar or
two would not force any decision on the end user, it would simply save them a trip.
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