I (currently) use the following macro:
<macrodef name="sub">
<attribute name="dir"/>
<attribute name="target"/>
<sequential>
<exec executable="bash"
dir="@{dir}"
failonerror="yes">
<arg value="-c"/>
<arg value="ant -emacs @{target}"/>
</exec>
</sequential>
</macrodef>
which I use with the following macro:
<macrodef name="dirs">
<attribute name="target"/>
<sequential>
<ac:for param="dir" list="${dirs}">
<sequential>
<sub dir="@{dir}" target="@{target}"/>
</sequential>
</ac:for>
</sequential>
</macrodef>
in each directory with a list of sub-project directories I use a build
file like:
<project name="apas_server">
<property name="dirs" value="fw,ws,aes,lws2s,server"/>
<import file="../build.xml"/>
</project>
I like to keep each project's ant instance to use a different jvm - so
there is no leakages of properties, references, class-loaders or types.
Peter
On 4/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>+ * add a <antfork> task that runs a completely new ant
>process, with different env, maybe even JDK. Sometimes people
>need this; running forrest builds is just one example. We'd
>use <java> to set it up.
I would prefer enhancing <ant> with fork and jvm attribute, like <java>.
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
