Return-Path: 
 <ant-dev-return-14718-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 50117 invoked by uid 500); 12 Jun 2001 15:43:48 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
list-help: <mailto:ant-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 50083 invoked from network); 12 Jun 2001 15:43:47 -0000
Message-ID: <3B2637D2.1050109@arielpartners.com>
Date: Tue, 12 Jun 2001 11:40:02 -0400
From: Craeg K Strong <cstrong@arielpartners.com>
Organization: Ariel Partners LLC
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:0.9.1) Gecko/20010607
X-Accept-Language: en-us
MIME-Version: 1.0
To: ant-dev@jakarta.apache.org
Subject: Re: [PROPOSAL] new propertyprecedence attribute for <ant> task
References: <00d101c0f33d$7cd851c0$da76883e@viquity.com>
	<3B26135B.F2240905@somanetworks.com> <m31yopafy6.fsf@bodewig.bost.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Stefan Bodewig wrote:

>Glenn McAllister <glenn@somanetworks.com> wrote:
>
>>This is a not unreasonable feature to ask for.
>>
>
>No, it is not.
>
>But I'm with Conor and Jose Alberto here - if we should happen to
>agree upon property passing from parent builds to sub builds for Ant2
>(we could try) and it is possible to keep the current behavior for
>Ant1 as a default, we should better do the same for Ant2 and Ant1.
>
>Say we have
>
><ant ...>
>  <property ...>
></ant>
>
>like Conor suggests (or keep the param syntax like Jose Alberto
>suggests) then we can add a flag that says "pass all properties" and
>make that default to true in Ant1 (and to false in Ant2).
>
>Stefan
>
I like this-- selective property passing is a great idea!    However, to 
support the behavior I
described you would still/also need some kind of override directive.  In 
this way I can pass
(certain) properties to the child and have the child _maybe_ override.   
The particular example
I have in mind has a parent buildfile that calls 12 different 
buildfiles, a few of which need to override
some of the defaults.  Would you object to having all of the above 
functionality?    
You end up with something like the following:

<ant   passallproperties="true" propertyoverride="child">
   <param...>
     <param...>
</ant>

--Craeg

-- 
Craeg K. Strong                               | www.arielpartners.com
Ariel Partners LLC		              | cstrong@arielpartners.com 
85 River Street, Ste. 3A                      | Fax:      (781) 647-9690
Waltham, MA 02453                             | Voice:    (781) 647-2425