[
https://issues.apache.org/jira/browse/HADOOP-12480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959188#comment-14959188
]
Chris Nauroth commented on HADOOP-12480:
----------------------------------------
It is possible for a change in a module to introduce a Javadoc warning in
another module that depends on it, but is not touched by the patch. For
example, suppose a patch renames a method in module A, and module B depends on
module A. If module B has Javadoc comments with {{@link}} or {{@see}} tags
pointing to the old method name, then it becomes a Javadoc warning in module B.
I'm not opposed to the change though. This might be another case where the
whole community needs to pay more attention to the nightly builds instead of
just pre-commit to catch problems like this.
> Run precommit javadoc only for changed modules
> ----------------------------------------------
>
> Key: HADOOP-12480
> URL: https://issues.apache.org/jira/browse/HADOOP-12480
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Vinayakumar B
> Assignee: Vinayakumar B
> Attachments: HADOOP-12480-01.patch, HADOOP-12480-02.patch,
> HADOOP-12480-03.patch, HADOOP-12480-04.patch
>
>
> Currently Precommit javadoc check will happen on root of hadoop,
> IMO Its sufficient to run for only changed modules.
> This way Pre-commit will take even lesser time as Javadoc will take
> significant time compare to other checks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
