Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Message-ID: <3A947A94.7C3F6F58@richardhall.net>
Date: Wed, 21 Feb 2001 19:33:56 -0700
From: "Richard S. Hall" <heavy@richardhall.net>
Organization: Freie =?iso-8859-1?Q?Universit=E4t?= Berlin
MIME-Version: 1.0
To: ant-user@jakarta.apache.org
Subject: Re: Two issues
References: <67FE02381F67D3119F960008C7845A2C0201D079@nt_syd_ex09.macbank>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tim Vernum wrote:

> That's not quite the way it is though.
> There is no parent/child relationship, there is just an order of execution.
>
> The "dependent" is actually executed first, (due to the nature of dependency)
>  and therefore has first stab at the cherry. This is not a result of some
>  "parent"/"child" relationship the way that
>         commandline => parent-script => project => target
>  works, it is just a result of persistence and immutability of properties.

But, by definition, this is not caused by the order of execution, it is caused
because the depending target is subordinate to the dependent target.  That is why
my two targets that don't depend on each other (but have the same property
${my.name}) each have their own value for that property, even if one is executed
before the other.

-> richard