> -----Original Message----- > From: Diane Holt [mailto:[EMAIL PROTECTED] > Sent: Sunday, January 14, 2001 3:14 PM > To: [EMAIL PROTECTED] > Subject: RE: Property substitutions, Contributed Tasks, & New features > > > --- Joshua Davis <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] http://pgmjsd.weblogs.com
