Johan Philippe - 2005-03-21

Logged In: YES

The problem actually lies with the underlying BuildDepency
tool that is used. You can reproduce this same type of
problem standalone if you try to run more than one tini
task in the same build file.
There is a workaround available by using the "fork" option
of the java task. The following is an example of how to use
this option

<tini outputfile="${dist.home}/${}"
dependencyfile="${tini.depend.txt}" fork="true"
failonerror="true" classpath="${tini.jar}">
<convert dir="${build.home}/classes"/>
<depend name="I2CAll"/>
<pathelement location="${tini.modules.jar}"/>