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=33143>. 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=33143 ------- Additional Comments From [EMAIL PROTECTED] 2005-02-07 12:16 ------- The design I have in mind is that the commons-logging implementation for the logger you're using must reside in the same classloader hierarchy as the logger implementation. This is why the -api JAR is used. As java.logging is available in the root classloader, so does its commons-logging impl, and it is located next to it in the classloader hierarchy (from Tomcat perspective; actually, it's one layer above it). Given the size of both projects (a couple hundred of lines of code each, it seems), UGLI is a fork of commons-logging. It demonstrates unwilligness to work with anyone else's API, and willingness to split the logging APIs again. If this is not your intention, then fine, but I need to see positive results. I am not involved in commons-logging development, and thus I view the situation as a user, and care only about the results. BTW, the log4j commons-logging implementation was developed by Costin, Craig, and Robert, with only one really simple patch from Ceki, contributed for commons-logging 1.0.4 (removing the need for a log4j 1.2 compatibility flag). I remember attempts by Ceki to torpedo commons-logging when the project was started, however. So I don't call this contributing to commons-logging, sorry. Do you have any more FUD for us to enjoy ? Basically, I now consider the existence of the log4j API harmful at this point. The loggers implementation, etc, are all good, but I hope you understand that if the thin API layer at the top was standardized, everyone would benefit. -1 for UGLI. -- 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]
