Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 29 Jul 2011 13:33:13 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1360754219.18487.1311946393899.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1548256092.246.1310998318671.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7468) hadoop-core JAR contains a
 log4j.properties file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran updated HADOOP-7468:
-----------------------------------

    Attachment: hadoop-7468-for-204.patch

This is the same patch for the 0.20.204 branch

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