>From another non commiter: I would also like to see it in. It would save me having lots of silly variables all over just for the sake of passing some value for one task to the next.
> -----Original Message----- > From: Shatzer, Larry [mailto:[EMAIL PROTECTED] > Sent: 22 October 2003 00:04 > To: 'Ant Developers List' > Subject: RE: Vote: <local> for 1.6 > > > Since I am not a commiter, my vote won't count, but I am +1 > for this. It solves my original problem perfectly. > > -- Larry > > > -----Original Message----- > > From: peter reilly [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, October 21, 2003 8:36 AM > > To: [EMAIL PROTECTED] > > Subject: Vote: <local> for 1.6 > > > > > > Hi all, > > > > I would like to put the local property patch into ant 1.6. > > > > Normally I would wait for 1.7 for this, but it has a big > > and (I think) beneficial impact on <macrodef/>. > > > > The changes to macrodef are not Backward Compatible > > with the current implementation. > > > > The <local> task declares properties that only exist > > for the current scope, where scope is a target, or > > a sequential (any taskcontainer) or a macro instance. > > > > The patch is in > > http://issues.apache.org/bugzilla/show_bug.cgi?id=23942 > > > > Peter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
