On Tuesday 28 October 2003 17:39, Dominique Devienne wrote:
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> >
> > It appears that the attributes as local properties
> > patch
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=23942
> >
> > causes macrodef to behave in the way you expect.
> From: Dominique Devienne [mailto:[EMAIL PROTECTED]
>
>
> > From: peter reilly [mailto:[EMAIL PROTECTED]
> >
> > It appears that the attributes as local properties
> > patch
> >
> > http://issues.apache.org/bugzilla/show_bug.cgi?id=23942
> >
> > causes macrodef to behave in the way you expect
> From: peter reilly [mailto:[EMAIL PROTECTED]
>
> It appears that the attributes as local properties
> patch
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=23942
>
> causes macrodef to behave in the way you expect.
>
> A cut-down version shows this.
>
>
Let me add:
>
I have had a quick look at this.
It appears that the attributes as local properties
patch
http://issues.apache.org/bugzilla/show_bug.cgi?id=23942
causes macrodef to behave in the way you expect.
A cut-down version shows this.
name="a" value="${a}"
n
Sorry to say I wasn't involved in the discussion at that time. What
were the arguments against using an alternative notation?
-Original Message-
From: Dominique Devienne [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 9:33 AM
To: 'Ant Developers List'
Subject: RE
> From: Steve Cohen [mailto:[EMAIL PROTECTED]
>
> You're correct about working around this problem. However, I think it's
> still a problem that the same
> ${identifier} notation can either indicate a macrodef attribute or an
> ant property with completely different times of resolution.
>
> In o
to Fernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 5:37 AM
To: Ant Developers List
Subject: RE: Tale from the front: macrodef nesting
> From: Steve Cohen [mailto:[EMAIL PROTECTED]
>
> I am now trying to experiment with some of the new features
> of ant 1.6. He
> From: Steve Cohen [mailto:[EMAIL PROTECTED]
>
> I am now trying to experiment with some of the new features
> of ant 1.6. Here's a real-world example of the difficulties
> of trying to replace antcalls with macrodefs.
>
> Given the following definitions, notice that I am trying to
> nest a
