[
https://issues.apache.org/jira/browse/HADOOP-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079300#comment-13079300
]
Steve Loughran commented on HADOOP-7468:
----------------------------------------
OK, this will have to become a "may break things" feature.
Todd, Why didn't you have your own log4j file? the one in hadoop.jar isn't
enough to turn your own logging on or off? Was it because with the hadoop.jar's
one in the way your own one didn't get picked up?
(IMO, half the problem here is log4j. It should log at info if there is no
file, instead of just telling you off. All other log frameworks do this)
> 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
