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=42647>. 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=42647 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO ------- Additional Comments From [EMAIL PROTECTED] 2007-07-25 21:27 ------- If I recall correctly log4j 1.2.13 had a bug that was corrected in 1.2.14 that resulted in DEBUG appearing when TRACE should have. The last example appears as if Jakarta Commons Logging is being used (note the class Log instead of Logger). Jakarta Commons had a TRACE level before log4j 1.2 did and so it just made the equivalent debug calls. Recent versions of Jakarta Commons Logging I believe keep TRACE as a distinct level when running against later log4j versions, but I don't follow JCL development that closely. I'm marking the bug as NEEDINFO for now. If the problems still appear with the latest Jakarta Commons Logging or log4j 1.2.15 release candidate, please provide the info. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
