Summary: | <parallel> task needs cascade option | ||
---|---|---|---|
Product: | Ant | Reporter: | Oliver Dungey <odungey> |
Component: | Core tasks | Assignee: | Ant Notifications List <notifications> |
Status: | NEW --- | ||
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 1.6.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Bug Depends on: | 28124, 16906, 25734 | ||
Bug Blocks: |
Description
Oliver Dungey
2004-04-01 12:40:07 UTC
Adding my other related bugs as dependencies Some small points here, what do you mean by subtasks? You mean like in <parallel> <if> <istrue .../> <then> <task1/> </then> <else> <task2/> </else> </if> </parallel> Are task1 and task2 the subtask you are referring to? This one does not make sense to me at all. Or are you talking about dependency TARGETS executed when calling <antcall/>? Notice that <antcall/> executes in completely new execution environment. Including reparsing the buildfile. the execution of the target is completely unaware of weather the call happens inside a parallel or not. If you want to not execute dependencies in a call to <antcall/> you need to restructure your build to provide you with a target with no dependencies. Now if you are talking about something else, please give an example. Sorry, I badly worded this. I was referring to this scenario: <target name="someothertarget" depends="1,2,3etc"> </target> <target name="aTarget"> <parallel> <antcall target="someothertarget" inheritall="true"/> </parallel> </target> ... but I have now been told that the <parallel> does not continue into <antcall> as this is a new environment, not sure if this is documented though. |