Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 5 Sep 2011 23:06:09 +0000 (UTC)
From: "Tom White (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1506398460.18403.1315263969835.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1021340432.18016.1315252692698.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7612) Change test-patch to run tests for
 all nested modules
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated HADOOP-7612:
------------------------------

    Attachment: HADOOP-7612.patch

This patch makes a change to test top-level compilation, and run all tests under the base directory it is run from (or specified in --basedir). It also add a --run-tests option so developers can run tests using test-patch. 

> 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
>         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