Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Date: Sat, 16 Aug 2003 10:36:11 -0500
Subject: Re: [build] Only run tests if something changed?
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
From: Dain Sundstrom <dain@coredevelopers.net>
To: geronimo-dev@incubator.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <EC273167-CFB6-11D7-B36D-000A959D0312@yahoo.co.uk>
Message-Id: <5D20E846-CFFF-11D7-A756-000393DB559A@coredevelopers.net>

On Saturday, August 16, 2003, at 01:57 AM, James Strachan wrote:

> On Friday, August 15, 2003, at 11:03  pm, Dain Sundstrom wrote:
>
>> This is exactly what I want.  If I change anything in the module (at 
>> all) or if one of my dependencies is new, run all of the module 
>> tests, otherwise don't.
>
> Why not just run the tests in the module you're in?
>
> 	cd geronimo/modules/foo
> 	maven test
>
> I'm not aware of any mechanism for only running the tests in a module 
> if a dependent jar has changed. I wonder if the Continuum thingy  - 
> Continuous Integration for Maven - could handle this kinda thing.  Or 
> you could add this as a feature request in Maven's JIRA.

James that is not my point.  Right now time you build all of the tests 
run.  I would like the test to run in the default build target, but 
only if something changed in the module.  The are a bunch of ways to 
make this determination.  The easiest being to set a run-tests flag 
when we compile.  Alternatively, we could check if any file in the 
project and any dependency jar has changed since the last run.  Isn't 
there some sweet jelly code that can do this without a new feature 
request?

-dain

/*************************
  * Dain Sundstrom
  * Partner
  * Core Developers Network
  *************************/