hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3368) Can commons-logging.properties be pulled from hadoop-core?
Date Wed, 22 Oct 2008 00:46:47 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Chansler updated HADOOP-3368:
------------------------------------

    Component/s: build

> Can commons-logging.properties be pulled from hadoop-core?
> ----------------------------------------------------------
>
>                 Key: HADOOP-3368
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3368
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 0.19.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: 0.19.0
>
>         Attachments: hadoop-3368.patch
>
>
> In the root of hadoop-core.jar is a log4j.properties and a commons-logging.properties
> while this provides good standalone functionality to hadoop, it complicates anyone else
trying to control the logging, and use the libraries in-process.
> In particular, there is a commons-logging.properties file that selects Log4J as the back
end. This is not needed as
>  -log4j is automatically picked up if it is on the classpath 
>  -if it is not on the classpath, asking for it is generally considered bad form
> If you look at the commons-logging configuration details:
>  http://commons.apache.org/logging/guide.html#Configuration
> you will see that that such a properties file takes priority over any setting through
system properties, which makes it very hard to override the settings without adding multiple
commons-logging.properties files and playing with their priority settings 
> If you pull the commons-logging.properties file from hadoop-core log4j will still be
picked up by default, but it becomes easier for people to turn on different logging infrastructures
if they want to. It should have no visible impact on the end user experience (unlike pulling
log4j.properties)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message