[
https://issues.apache.org/jira/browse/HADOOP-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883468#comment-13883468
]
Hudson commented on HADOOP-10288:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #5048 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5048/])
HADOOP-10288. Explicit reference to Log4JLogger breaks non-log4j users.
Contributed by Todd Lipcon. (todd:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1561882)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/http/HttpRequestLog.java
> Explicit reference to Log4JLogger breaks non-log4j users
> --------------------------------------------------------
>
> Key: HADOOP-10288
> URL: https://issues.apache.org/jira/browse/HADOOP-10288
> Project: Hadoop Common
> Issue Type: Bug
> Components: util
> Affects Versions: 2.4.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 2.4.0
>
> Attachments: hadoop-10288.txt
>
>
> In HttpRequestLog, we make an explicit reference to the Log4JLogger class for
> an instanceof check. If the log4j implementation isn't actually on the
> classpath, the instanceof check throws NoClassDefFoundError instead of
> returning false. This means that dependent projects that don't use log4j can
> no longer embed HttpServer -- typically this is an issue when they use
> MiniDFSCluster as part of their testing.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
