hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1947) test-patch target for javadoc broken?
Date Thu, 12 Aug 2010 09:19:17 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897644#action_12897644
] 

Amareshwari Sriramadasu commented on MAPREDUCE-1947:
----------------------------------------------------

Chris, this jira is to fix hudson's test-patch target for javadoc. Currently it is not running
javadoc target at all.
The console output of one of the patch builds shows:
{noformat}
     [exec] 
     [exec] javadoc:
     [exec]     [mkdir] Created dir: /grid/0/hudson/hudson-slave/workspace/Mapreduce-Patch-h4.grid.sp2.yahoo.net/trunk/build/docs/api
     [exec]   [javadoc] Generating Javadoc
     [exec]   [javadoc] Javadoc execution
     [exec]   [javadoc] javadoc: error - Cannot find doclet class org.apache.hadoop.classification.tools.ExcludePrivateAnnotationsStandardDoclet
     [exec]   [javadoc] 1 error
     [exec] 
     [exec] BUILD SUCCESSFUL
     [exec] Total time: 48 seconds

{noformat}

> test-patch target for javadoc broken?
> -------------------------------------
>
>                 Key: MAPREDUCE-1947
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1947
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.22.0
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Giridharan Kesavan
>         Attachments: M1762-javadoc.patch
>
>
> Running "ant javadoc" in mapreduce trunk gives following warning:
> {noformat}
>   [javadoc] /home/amarsri/workspace/mapreduce/src/java/org/apache/hadoop/mapreduce/Counter.java:125:
warning - @param argument "the" is not a parameter name.
> {noformat}
> But test-patch did not complain for the patch build which introduced the warning, and
it did not complain for any further builds.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message