You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by Joshua Davis <js...@bellatlantic.net> on 2001/01/14 22:31:27 UTC

RE: Property substitutions (scoping)

> -----Original Message-----
> From: Diane Holt [mailto:holtdl@yahoo.com]
> Sent: Sunday, January 14, 2001 3:14 PM
> To: ant-dev@jakarta.apache.org
> Subject: RE: Property substitutions, Contributed Tasks, & New features
>
>
> --- Joshua Davis <js...@bellatlantic.net> wrote:
> > Is <property> allowed inside <task>, currently?
>
> As far as I know, a nested <property> tag is allowed inside an <ant> task
> (as opposed to a nested <param> tag inside an <antcall> task), and it's
> allowed as an attribute to the <available> and <uptodate> tasks, although
> the <uptodate> task doesn't allow for a value -- it always just sets the
> property to "true" (<available> only defaults to "true" -- you can specify
> a value for it if you want).

Right.  Do the <property> elements inside <ant> set properties in the scope
of the nested ant project?  I guess what I'm getting at is:  If properties
have better scoping control (+1 by me), does this imply lexical or dynamic
scoping, or both?

'spose I could try it ;->

Josh Davis
jsd2000@bellatlantic.net
http://pgmjsd.weblogs.com