ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Java5 move and Jenkins
Date Fri, 09 Mar 2012 04:57:07 GMT
On 2012-03-09, Jesse Glick wrote:

> On 03/08/2012 12:04 AM, Stefan Bodewig wrote:
>> do we have to do anything special to provide the Jenkins build with a
>> ${} that it actually is allowed to write to?

> Using ${} from tests is a bit dangerous anyway; the
> files may rarely or never get cleaned up,

the tearDown target should take care of that, unless anything kills Ant,
that is.

> you need to consider possible race conditions between different jobs
> running on the same node, etc.

True.  I guess we never envisoined that.

> Can the tests be made to use a tempdir inside the ${basedir}
> somewhere?

Several JUnit tests use (need to grep through it), most
if not all AntUnit tests import a common file that defines the setUp and
tearDown targets and properties input and output which the tests use.
If you change that file (src/tests/antunit/antunit-base.xml) it should
take effect for a whole bunch of AntUnit tests immediately.

> By comparison, most NetBeans unit tests use a utility
> NbTestCase.getWorkDir() [1] which takes a static root
> (e.g. ${basedir}/build/test/unit/work/) and appends a suffix based on
> the test suite & case names. For tests needing File access this is
> very convenient.

That would work for our JUnit tests, for AntUnit we'd have the build
file name (the one importing the base file) but not the executing


> [1]

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

View raw message