DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13201>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13201 Remove default log4j configuration ------- Additional Comments From [EMAIL PROTECTED] 2002-10-22 17:44 ------- Not for me. I use log4j, but it's not configured using the default configuration mechanism. I configure explicitly, and not always from a property file name 'log4j.properties'. How about this? If we're searching for a log implementation, that is,an implementation has not been set explicitly, and the log4j Root appender is not configured, move on to the next in the search list? I'd also like to know what Steven Caswell's desired behavior is? He's got the use case where Root is unconfigured, but other loggers are. What should a random log category do in this case. Be default, I believe Log4J will print out error messages, which is, in my opinion, undesireable behavior. -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
