ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Reilly <peter.rei...@corvil.com>
Subject Re: Suggested using.html diff
Date Tue, 16 Mar 2004 10:04:02 GMT
Committed, thanks.
Peter

Jack Woehr wrote:

>I think this is more accurate in detail than what stands now.
>
>--
>Jack J. Woehr            # "[F]ar in the empty sky a solitary esophagus slept
>http://www.well.com/~jax #  upon motionless wing; everywhere brooded stillness,
>http://www.softwoehr.com #  serenity, and the peace of God." - Mark Twain
>
>
>  
>
>------------------------------------------------------------------------
>
>? using.html.diff
>Index: using.html
>===================================================================
>RCS file: /home/cvspublic/ant/docs/manual/using.html,v
>retrieving revision 1.33
>diff -c -r1.33 using.html
>*** using.html	9 Feb 2004 21:50:05 -0000	1.33
>--- using.html	12 Mar 2004 19:24:43 -0000
>***************
>*** 77,84 ****
>  <code>depends</code> attribute, you
>  might think that first target C, then B and then A is executed.
>  Wrong! C depends on B, and B depends on A, so first A is executed, then B, then C, and
finally D.</p>
>! <p>A target gets executed only once, even when more than one target
>! depends on it (see the previous example).</p>
>  <p>A target also has the ability to perform its execution if (or
>  unless) a property has been set. This allows, for example, better
>  control on the building process depending on the state of the system
>--- 77,92 ----
>  <code>depends</code> attribute, you
>  might think that first target C, then B and then A is executed.
>  Wrong! C depends on B, and B depends on A, so first A is executed, then B, then C, and
finally D.</p>
>! <p>In a chain of dependencies stretching back from a given target such
>! as D above, each target gets executed only once, even when more than
>! one target depends on it. Thus, executing the D target will first
>! result in C being called, which in turn will first call B, which in
>! turn will first call A. After A, then B, then C have executed,
>! execution returns to the dependency list of D, which will <u>not</u>
>! call B and A, since they were already called in process of dependency
>! resolution for C and B respectively as dependencies of D. Had no such
>! dependencies been discovered in processing C and B), B and A would
>! have been executed after C in processing D's dependency list.</p>
>  <p>A target also has the ability to perform its execution if (or
>  unless) a property has been set. This allows, for example, better
>  control on the building process depending on the state of the system
>
>  
>
>------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>For additional commands, e-mail: dev-help@ant.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message