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=37954>. 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=37954 ------- Additional Comments From [EMAIL PROTECTED] 2005-12-18 19:01 ------- As you have already noted the error messages have been improved in the code currently in SVN. There is also a new internal diagnostics feature. From the release notes: * added internal diagnostics feature. If commons-logging is behaving in an unexpected manner, you can now set system property org.apache.commons.logging.diagnostics.dest to the value STDOUT, STDERR or a filename. As commons-logging initialises itself for each new contextClassLoader it detects, useful information will be output about which logging library is bound to and why. 1. Guessing in which jar the specifiedLogClassName is included in, is a tricky thing to do. Since anyone can write their own Log implementation and package it any way they see fit. 2. If the underlying logging system is not configured properly, I would say that it is up to that system to report what might be wrong. 3. Searching is done using the classpath of the classloader that loaded commons-logging 4. Not sure what you mean here... -- 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]
