Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 76611 invoked by uid 500); 24 Jul 2001 14:53:14 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 76369 invoked from network); 24 Jul 2001 14:53:14 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Peter Donald To: ant-dev@jakarta.apache.org Subject: Re: Introduction of Multithreading Date: Wed, 25 Jul 2001 00:46:52 +1000 X-Mailer: KMail [version 1.2] References: <004301c112b4$e6027ae0$6ce1223f@cognetnt> <01072300131107.00754@helm.realityforge.org> In-Reply-To: MIME-Version: 1.0 Message-Id: <01072500465203.00772@helm.realityforge.org> Content-Transfer-Encoding: 8bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Wed, 25 Jul 2001 00:48, Stefan Bodewig wrote: > On Mon, 23 Jul 2001, Peter Donald wrote: > > It also would produce surprising results if people were expecting > > properties to behave the same as they do elsewhere in the build > > file. > > I must be missing something here, aren't properties behaving exactly > the same as they do everywhere else in the build file? > > The first property task wins (but you cannot be sure, which one may be > the first, of course). Properties defined outside are available in > the container and vice versa. In what way are they different? My test file terned out to have a typo and so I assumed that properties where set are parse time for subelements - but I guess I was wrong ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*