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 10:30:02 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 stevencaswell@apache.org  2002-10-23 10:30 -------
The functionality I desire is the functionality in version 1.0 of
commons-logging. That functionality is that commons-logging makes no attempt in
any way to apply a default configuration to log4j. And that is the fundamental
issue I have against having commons-logging attempt to put in a default
configuration - it shouldn't. As a developer or deployer, I should be smart
enough to know what I want my logging system to acheive.

Again, quoting from the commons-logging documentation:

"The basic principle is that the user is totally responsible for the
configuration of the underlying logging system. Commons-logging should
not change the existing configuration."

Existing configuration means whatever I've done to configure my logging package,
including letting it default.

--
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