hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nkeywal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7349) Jenkins build should compare trunk vs patch for Javadoc warnings
Date Tue, 18 Dec 2012 17:40:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535088#comment-13535088
] 

nkeywal commented on HBASE-7349:
--------------------------------

Yes, that's what I've finally done in HBASE-7363, it worked both times.
For the generics, I checked, it's official: you need to erase the types in the javadocs.
For the ZooKeeperProtos.Table.State, I believe it's because it's a generated code excluded
from the javadocs, but I'm not sure...
                
> Jenkins build should compare trunk vs patch for Javadoc warnings
> ----------------------------------------------------------------
>
>                 Key: HBASE-7349
>                 URL: https://issues.apache.org/jira/browse/HBASE-7349
>             Project: HBase
>          Issue Type: Improvement
>          Components: build
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>         Attachments: 7349-build-improve-javadoc-warnings.0.diff
>
>
> The javadoc check should look for an increase in the number of warnings. It can do so
by running javadoc against trunk before running it for the patch. This will increase build
times.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message