[
https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101160#comment-13101160
]
Hudson commented on HADOOP-7612:
--------------------------------
Integrated in Hadoop-Hdfs-trunk #788 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/788/])
HADOOP-7612. Change test-patch to run tests for all nested modules.
tomwhite :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1166848
Files :
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> Change test-patch to run tests for all nested modules
> -----------------------------------------------------
>
> Key: HADOOP-7612
> URL: https://issues.apache.org/jira/browse/HADOOP-7612
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: Tom White
> Assignee: Tom White
> Fix For: 0.23.0
>
> Attachments: HADOOP-7612.patch
>
>
> HADOOP-7561 changed the behaviour of test-patch to run tests for changed
> modules, however this was assuming a flat structure. Given the nested maven
> hierarchy we should always run all the common tests for any common change,
> all the HDFS tests for any HDFS change, and all the MapReduce tests for any
> MapReduce change.
> In addition, we should do a top-level build to test compilation after any
> change.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
