[
https://issues.apache.org/jira/browse/HADOOP-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079302#comment-13079302
]
Steve Loughran commented on HADOOP-7468:
----------------------------------------
Todd -is there an HDFS issue here I can xref to? I don't want to put the log4j
file as that stops any hadoop client app from controlling its own logging. I'd
rather fork a copy of the log4j file into hdfs/src/test and give you the power
to tune it. And for that I need an HDFS issue. (and I need to get the M3 core
build working locally)
> 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
