]
Steve Ebersole commented on HHH-3753:
-------------------------------------
My point was more whether this affects the slf4j-api artifact? Is LoggerFactory part of
slf4j-api?
Upgrade to SLF4J version 1.5.6
------------------------------
Key: HHH-3753
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-3753
Project: Hibernate Core
Issue Type: Improvement
Components: core
Reporter: Ceki Gulcu
Assignee: Steve Ebersole
Fix For: 3.3.x, 3.5
I would like to suggest that hibernate upgrade to SLF4J version 1.5.6 (the trunk
currently uses 1.5.2). Several important bugs were fixed between 1.5.2 and 1.5.6. Just as
importantly, 1.5.6 is more tolerant when there is a mismatch between the slf4j-api and its
binding (e.g. slf4j-log4j12). The version mismatch problem (see [1]) seems to pose
problems to several users.
We are taking this issue seriously. SLF4J version 1.5.6 mitigates this problem by
alerting the user about SLF4J version mismatches. (Thus, instead of a mysterious
exception, the user gets an explanation pinpointing the problem.) We are also working on
making slf4j-api and its bindings to mix and match independenly of their versions.
Anyway, I think upgrading to SLF4J 1.5.6 would benefit hibernate users.
[1]
http://slf4j.org/faq.html#compatibility
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: