hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (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:28:15 GMT

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

Nick Dimiduk commented on HBASE-7349:
-------------------------------------

[~nkeywal] Remove the generics from the first set. Try simply {{RegionObserver#preFlush(ObserverContext,
HStore, KeyValueScanner)}}

The {{ZooKeeperProtos.Table.State}} I'm not sure about either. Maybe just use {{\{\@code\}}}
instead?
                
> 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