[EMAIL PROTECTED] wrote:
<target name="b"> <taskb1> <parallel> <taskb2> <taskb3> </parallel> </target> you'll get the following dependencies among the _tasks_: taskb1: -none- taskb2: taskb1 taskb3: taskb1where is <parallel> ? Just for annotating? taskb1 : -none- parallel: taskb1 and the execution of 'parallel' would be taskb2: - none- taskb3: taskb2 so just sequential ...
If you delimit the number of threads to one - you would get a single-threaded solution ;) but where is the disadvantage? Is there any deadlock? The build should process ... Jan
The <parallel> and <sequential> elements would be rather regarded as syntactic constructs than actual tasks *IN THIS MODEL*. Generally, a build script _must_ be able to run successfully in a single thread environment. Therefore, it would be better to have an additional XML element that does not *demand* the parallel execution, but merely *allows* it. The same applies to the target level parallelism: declaring multiple targets as parallel (with whatever syntax) is simply an allowance.
Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
