ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Conor MacNeill" <co...@cortexebusiness.com.au>
Subject Re: [DISC] details of task library concept
Date Fri, 25 May 2001 12:42:53 GMT

----- Original Message -----
From: "Peter Donald" <donaldp@apache.org>
To: <ant-dev@jakarta.apache.org>
Cc: <ant-dev@jakarta.apache.org>
Sent: Friday, May 25, 2001 3:43 PM
Subject: RE: [DISC] details of task library concept


> At 06:16 AM 5/25/01 +0100, Jose Alberto Fernandez wrote:
> >> Ick. I don't think I like using namespace in this way. I can handle
> >> naespace for "static" structural aspects (ie indicating task
> >> library or
> >> aspect attribute/element) but it can get confusing to use
> >> namespace to also
> >> indicate other projects.
> >>
> >
> >Well this are not really XML name-spaces, since they are on the
attribute
> >values. Not the attribute names. In any case, if we are going to include
> >things in one another we will need to have a name dereferencing
operator. In
> >this case is ":" but it could have been anything else ( "^" "->" "!" ).
>
> Excellent - I like.
>
> Static namespaces (ie task/aspect) allocation uses ':' for resolution
> Dynamic instance namespaces (ie other projects) allocation uses '->' for
> resolution (I prefer this over '.' as '.' is commonly used in names of
> properties).
>
> So we would now have something like
>
> <target name="foo" depends="otherPrj->before-foo, otherPrj->before-foo2">
>   <echo message="Here is the value of public property blah.present"/>
>   <echo message="in project 'Other': ${otherPrj->blah.present}"/>
> </target>
>
> Thoughts?
>

+1 - works for me.

Conor



Mime
View raw message