Please refer to the commented version
<http://jakarta.apache.org/ant/ant2/features.html> instead of the
"raw" <http://jakarta.apache.org/ant/ant2/requested-features.txt> when
searching for explanations 8-)
Sean McNamara <[EMAIL PROTECTED]> wrote:
> My understanding is that multiple commnads within a task will be
> multithreaded, the multiple threads will be joined at the end of the
> containing task.
"within a target", not "whithin a task" - and only if you ask for it.
> <task name="startAllServers" multithread="yes">
> <startServer name="server1" ... />
> <startServer name="server2" ... />
> <startServer name="server3" ... />
> </task>
Probably more something like
<target name="startAllServers">
<parallel>
<startServer name="server1" ... />
<startServer name="server2" ... />
<startServer name="server3" ... />
</parallel>
</task>
But details have not yet been defined.
> The second type of multithreading (which was rejected) would allow
> us to multithread entire tasks, meaning the build process wouldn't
> stop and wait for a return.
Nope. The one that has been rejected was something like the
following. Consider
<target name="A" />
<target name="B" />
<target name="C" depends="A,B" />
as A and B have no explicit dependency on each other they could be run
in parallel when you want to prepare for C. In reality many people
will rely upon A to be run before C. Furthermore many tasks (and to a
certain extent Ant's core) have not been designed with multithreading
in mind, so this would be more than a bit dangerous.
This has been rejected for now, but could be added at some later point
in Ant development.
Stefan
