[
https://issues.apache.org/jira/browse/HADOOP-10288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882038#comment-13882038
]
Hadoop QA commented on HADOOP-10288:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12625206/hadoop-10288.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3472//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/3472//console
This message is automatically generated.
> 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
> 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)
