hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7468) hadoop-core JAR contains a log4j.properties file
Date Thu, 04 Aug 2011 11:33:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079331#comment-13079331
] 

Steve Loughran commented on HADOOP-7468:
----------------------------------------

Incidentally, before a new log4j.properties file is added, you can force commons-logging to
go through the java util logger (and hence log@info) by setting
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger

That's less than ideal, but is a quick workaround

> hadoop-core JAR contains a log4j.properties file
> ------------------------------------------------
>
>                 Key: HADOOP-7468
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7468
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.20.203.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: hadoop-7468-for-204.patch, hadoop-7468.txt
>
>
> the hadoop-core JAR in the distribution and in the Maven repositories has a log4j JAR.
This can break the logging of any client programs which import that JAR to do things like
DFSClient work. It should be stripped from future releases. This should not impact server-side
deployments, as the properties file in conf/ should be picked up instead. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message