Conor,
Thanks for posting the tutorial. It is an excellent explanation of the parts of Ant that are a struggle to figure out from just reading code and api docs. It alsow answered a question that I had posted a bug about -- the "extra" blank target in Ant 1.6. Not a bug, it's a design feature. Definitely continue working on these, they aer well worth the trouble.
Dale
Conor MacNeill wrote:
On Thu, 17 Apr 2003 02:43 am, Gus Heck wrote:
I agree. This is really cool. The section labeled "Top Level Tasks" seems to say that tasks on the top level are run at parse-time. Does this mean that the order of tasks at the top level is the order of execution, or do the old toplevel tasks still run first?
In 1.6 all top-level tasks are gathered, in build-file order, into an invisible target which is executed at the end of parsing (so technically, not at parse-time). There is no distinction between old top-level tasks and other tasks.
So, given this build, <project name="toplevel" default="main"> <echo message="Task 1 test.prop=${test.prop}"/>
<target name="main"> <echo message="Task 2 test.prop=${test.prop}"/> </target>
<property name="test.prop" value="fubar"/>
<echo message="Task 3 test.prop=${test.prop}"/>
</project>
the output is
Buildfile: build.xml [echo] Task 1 test.prop=${test.prop} [echo] Task 3 test.prop=fubar
main: [echo] Task 2 test.prop=fubar
BUILD SUCCESSFUL
So, still somethings to be careful about :-)
Conor
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
