[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696?page=c...
]
Steve Ebersole updated HHH-2696:
--------------------------------
Fix Version/s: 3.3
OK, Ceki says he has added this feature in slf4j trunk. And he plans on releasing 1.4.1
in the next few days including this feature. So lets schedule this move for Hibernate
3.3. Need to determine the best migration path in terms of whether to (1) use the bridge
concept to not change Hibernate code or (2) use search/replace in Hibernate code to use
the slf4j API.
Consider migrating to slf4j
---------------------------
Key: HHH-2696
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2696
Project: Hibernate3
Issue Type: Improvement
Components: core
Affects Versions: 3.2.4
Reporter: Koda Janh
Fix For: 3.3
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Please consider migrating away from commons-logging and onto slf4j for the reasons
mentioned here:
http://www.qos.ch/logging/classloader.jsp
The author of log4j went on to write "logback" which is an implementation of
slf4j that has much better performance than log4j and much cleaner output. I recommend you
evaluate these alternatives seriously and consider them for future releases of Hibernate.
To ease migration you could use the "log4j bridge" mentioned here:
http://logback.qos.ch/bridge.html
You simply replace log4j's jar by the bridge jar and all log4j method calls get
redirected to logback under the hood.
--
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