You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (Commented) (JIRA)" <ji...@apache.org> on 2012/02/21 15:16:37 UTC

[jira] [Commented] (HADOOP-7468) hadoop-core JAR contains a log4j.properties file

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

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

the log4j files should all have been purged from trunk and the artifacts that get stuck in the maven repos on the 0.23.x branch, which addresses my needs...
                
> 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: Sub-task
>          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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira