ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <>
Subject Re: [GUMP@vmgump]: Project ant-testutil (in module ant) failed
Date Fri, 07 Jul 2006 09:15:35 GMT
Gump Integration Build wrote:
> To whom it may engage...
> This is an automated request, but not an unsolicited one. For 
> more information please visit, 
> and/or contact the folk at
> Project ant-testutil has an issue affecting its community integration.
> This issue affects 5 projects,
>  and has been outstanding for 2 runs.
> The current state of this project is 'Failed', with reason 'Build Failed'.
> For reference only, the following projects are affected by this:

Gump can not only tells us who depends on it, it even emails the details.

>     - ant-testutil :  Java based build tool
>     - antunit-test :  Task and Type Libraries for Apache Ant
>     - dotnet-antlib-test :  Task and Type Libraries for Apache Ant
>     - smartfrog-tasks-test :  Smartfrog: Application Deployment from HP Laboratories
>     - svn-antlib-test :  Task and Type Libraries for Apache Ant

Those are all ant-internal projects other than smartfrog-tasks-test, and 
I've just audited that one.


Actually I had overridden it in about 6 test cases, all to 
executeTarget("teardown"). Given that BuildFileTest.tearDown executes 
target "tearDown" if present, I could delete all the the teardown 
methods (now all marked as public, btw), and rely on the base to clean 
up. Has that conditional tearDown target execute been in there since ant1.5

anyway, this shows why we can't easily loosen the scope of the 
operation; things will break. We could rely on the no-stability warning 
of ant-testutils and do it anyway....


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message