[
https://issues.apache.org/jira/browse/HADOOP-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076053#comment-14076053
]
Hadoop QA commented on HADOOP-10884:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12658112/HADOOP-10884.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc 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 2.0.3) 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/4370//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4370//console
This message is automatically generated.
> Fix dead link in Configuration javadoc
> --------------------------------------
>
> Key: HADOOP-10884
> URL: https://issues.apache.org/jira/browse/HADOOP-10884
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 2.0.2-alpha
> Reporter: Akira AJISAKA
> Assignee: Akira AJISAKA
> Priority: Minor
> Labels: newbie
> Attachments: HADOOP-10884.patch
>
>
> In [Configuration
> javadoc|http://hadoop.apache.org/docs/r2.4.1/api/org/apache/hadoop/conf/Configuration.html],
> the link to core-default.xml is dead. We should fix it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
