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 13201] - Remove default log4j configuration
Date Wed, 23 Oct 2002 02:52:29 GMT
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 steve.downey@netfolio.com  2002-10-23 02:52 -------
 I didn't mean that log4j in an application couldn't be used without a root logger configured.
That's well within scope for log4j and a self contained application.   But what should the
semantics be for an application that uses a component that uses commons-logging that doesn't
have a root appender configured? When the component goes to log, it will get an unconfigured
category, and will generate errors. It might not even be the component that's of interest
to the application. e.g. httpclient may use collections, which uses logging.   By leaving
log4j unconfigured, we force the application to become interested in logging. And removing
log4j is not always feasible. It may be present to support other apps that are interested
in logging.   Getting log4j warnings just because you start using a commons component seems
wrong.

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


Mime
View raw message