#2 Dependency file basedir problem

[Anonymous]

TiniAnt is used in two environments, with Ant executing
standalone and with Ant integrated and executing from
NetBeans IDE. Build script works perfectly in
standalone. When executed from NetBeans, <tini> task
complains twice that it cannot find dependency files (3
are specified). Only the dependency files with relative
pathnames are errored which was discovered by
explicitly converting them to absolute pathnames.
Echoing ${basedir} before the <tini> task showed it to
be correct. Using explicit ${basedir} macros on the
relative paths in dependencyfiles worked correctly as
well. In this environment, it appears that the basedir
handling of relative pathnames for dependency files has
a small problem when Ant is executed in the same VM as
the IDE instead of in its own VM. BTW, the script is
the stock Tynamo 0.11 build.xml.

Bill Meine
wmeine@mindspring.com

[Johan Philippe]

Logged In: YES
user_id=114892

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}/${tini.name.hello}"
database="${tini.db}"
mainclass="${main.class.hello}"
dependencyfile="${tini.depend.txt}" fork="true"
failonerror="true" classpath="${tini.jar}">
<convert dir="${build.home}/classes"/>
<depend name="I2CAll"/>
<dependpath>
<pathelement location="${tini.modules.jar}"/>
</dependpath>
</tini>