commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz" <>
Subject Re: [collections] Running the tests
Date Tue, 16 Sep 2003 03:41:58 GMT
Henri Yandell wrote:
> As long as 'ant test' and 'maven jar' run all the unit tests [rather than
> any performance tests] I don't mind what's going on.
> I'm -1 to 'ant test'/'maven jar' not running all the tests, and hadn't
> realised  it wasn't running them all.

Janek's patch ( 
will fix the ant build to run all tests using TestAllPackages as the 
entry point.  The corresponding change should be made for maven (using 
TestAllPackages, non **/  I will do this if there are no 

> Hen
> On Mon, 15 Sep 2003, Rodney Waldhoff wrote:
>>I'm think -1 to forcing the user to use "**/" to
>>select the unit test suite to execute.  What's the harm in giving the user
>>a way to execute the full test suite without using Ant/Maven or an IDE to
>>inspect the filesystem for Test classes?
>>On Sat, 13 Sep 2003, Phil Steitz wrote:
>>>Currently neither the ant nor maven [collection] builds runs the
>>>subpackage tests. Janek Bogucki just submitted a patch
>>>( to change the
>>>entry point to the ant test target from TestAll (just the top level) to
>>>TestAllPackages. I have locally modified project.xml to include
>>>**/  I would like to commit these changes.  Any objections?
>>>Also, why not dispense with the ant entry point (and TestAllPackages)
>>>and just use **/ to select tests?  What am I missing here?
>>- Rod <>
>>To unsubscribe, e-mail:
>>For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View raw message