Return-Path: 
 <ant-dev-return-14394-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 88903 invoked by uid 500); 5 Jun 2001 10:43:18 -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 88418 invoked from network); 5 Jun 2001 10:43:16 -0000
From: "Jose Alberto Fernandez" <j_a_fernandez@yahoo.com>
To: <ant-dev@jakarta.apache.org>
Subject: RE: Scope of Types
Date: Tue, 5 Jun 2001 11:44:40 +0100
Message-ID: <000b01c0edac$869c1e30$da76883e@viquity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <m3itibushg.fsf@bodewig.bost.de>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

> From: Stefan Bodewig [mailto:bodewig@apache.org]
>
> Jose Alberto Fernandez <j_a_fernandez@yahoo.com> wrote:
>
> >> From: Stefan Bodewig [mailto:bodewig@apache.org]
>
> >> >><projectref name="A">
> >> >>  <A:mailaddressset id="send-report-to">
> >> >>    <address to="bodewig@apache.org" />
> >> >>  </A:mailaddressset>
> >> >></projectref>
> >> >
> >
> > 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.
>

Well, the current rules would require <projectref> to allow for a
<A:mailaddressset> element. But you cannot have it because is dynamically
generated. I would seem that we need something like <param> that allows for
any datatype element specification inside. Much like the <set-item>
operation I think Peter was talking about.

This kinds of issues is what makes me think we are making some funny
distinctions between <properties> and <typedefs>. There seem to be some
missing unifying concept for both. Maybe what was called <item>.

Jose Alberto