commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34437] - [logging] Log.trace() doesn't use log4j 1.3 trace methods
Date Wed, 28 Sep 2005 21:56:50 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34437>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34437





------- Additional Comments From joerg@j-hohwiller.de  2005-09-28 23:56 -------
two points from me:

1. As you can read on http://www.qos.ch/logging/preparingFor13.jsp on the long
run they want to kick out the legacy stuff such as Category and Priority.
So eighter we should kick this out completely (which is my suggestion) or we
have a very strong point for creating a separate Log4J13Logger which is already
in SVN
and is using Logger and Level.

2. The current SVN codebase has renamed Log4JLogger to Log4J12Logger. I am not
sure if this is a good idea for compatibility. If someone just upgrades the jar
and is using the Log4JLogger set up somewhere in his config, his code may not
work anymore (as expected).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message