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 Mon, 31 Mar 2003 00:00:06 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 craig.mcclanahan@sun.com  2003-03-31 00:00 -------
Picking up this thread as I'm reviewing commons-logging in prep for a 1.0.3 release.

I agree with Steven Caswell's original request -- commons-logging should make
absolutely no attempt to configure the underlying loggging implementation. 
Instead, either the app should preconfigure the implementation the way it wants,
or the implementation should provide a mechanism for self-configuration.

(Ceki, my understanding is that this is not true for Log4J, right?  If there's a
"log4j.properties" file then it will be used to configure things if config was
not done directly by the application?)

Further discussion about this will happen on COMMONS-DEV shortly.

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


Mime
View raw message