Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 68336 invoked by uid 500); 5 Jun 2001 10:32: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: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 68318 invoked from network); 5 Jun 2001 10:32:44 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: Scope of Types References: <000a01c0eda9$77f2ca30$da76883e@viquity.com> From: Stefan Bodewig Date: 05 Jun 2001 12:32:43 +0200 In-Reply-To: "Jose Alberto Fernandez"'s message of "Tue, 5 Jun 2001 11:22:47 +0100" Message-ID: Lines: 35 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Jose Alberto Fernandez wrote: >> From: Stefan Bodewig [mailto:bodewig@apache.org] >> >> Peter Donald wrote: >> >> > whats the difference between IDs and property values? >> >> Using something via refid implies a typed value, using ${} does not >> - especially if the defining project doesn't know the type project >> B will be using. > > This looks kind of artificial to me. why can't I say id="..." /> meaning the same thing as name="...." ? You can. I was talking about refid="..." vs. ${}. >> >> >> >> >> >>
>> >> >> >> >> > > > Here you are defining an id for 'A' within a pseudo-task, so the > blank rule about forbidding this sort of thing may not be > correct. Who said I wanted to forbid what? 8-) Datatypes shouldn't be treated different than properties, right? If I can define properties via param, I must have a way to define arbitrary data types and pass them to subbuilds or projectrefs as well IMHO. Stefan