You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Dennis Lundberg (JIRA)" <ji...@apache.org> on 2006/11/18 13:48:40 UTC
[jira] Resolved: (LOGGING-41) Remove default log4j configuration
[ http://issues.apache.org/jira/browse/LOGGING-41?page=all ]
Dennis Lundberg resolved LOGGING-41.
------------------------------------
Resolution: Fixed
> Remove default log4j configuration
> ----------------------------------
>
> Key: LOGGING-41
> URL: http://issues.apache.org/jira/browse/LOGGING-41
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: 1.0.1
> Environment: Operating System: All
> Platform: All
> Reporter: Steven Caswell
>
> I am requesting that the code added to Log4JCategory in
> commons-logging-1.0.1 that sets up a default initialization in log4j be
> removed.
> Why? When I put 1.0.1 in place of 1.0, I started getting extraneous
> messages logged to the console. Subsequent research led me to the new
> initialization code in Log4JCategory. The problem is in the way the
> initialization code tries to decide if log4j has been configured. It
> assumes that the root category has been configured with an appender. I
> happen to have a log4j properties configuration that doesn't configure
> an appender, so the initialization code couldn't tell that log4j had
> been configured, it created the default root appender, and I started
> getting the extraneous messages.
> I realize there are easy workarounds for my particular problem, but I
> believe this presents a more philosophical issue. Quoting from the
> commons-logging api org.apache.commons.logging package description:
> "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."
> The code in question directly violates this expressly stated principal
> and is inappropriate. Allowing this code to remain opens a Pandora's box
> of attempts to configure the underlying logger, which should be resisted
> based on the above principal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org