I like that idea. I think since you are already in <local-property> the locally scoped property should be used. At least to me, that makes the most sense. If you needed the non-local property, why even have it locally scoped when you call ant or antcall?
-- Larry > -----Original Message----- > From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED] > Sent: Friday, October 17, 2003 4:42 AM > To: Ant Developers List > Subject: RE: Macrodef and parallel in a recursive situation > > > For a long time I have thought on adding local contet to ANT. > In principle it would be something like: > > <target ....> > <property name="x" value="w"/> > <echo message="${x}"/> > ... > <local-property name="x"> > <!-- here ${x} has no value assigned to it > <echo message="${x}"/> > <property name="x" value="y"/> > <echo message="${x}"/> > </local-property> > <echo message="${x}"/> > ... > </target> > > The output of the above target would be something like: > [echo] w > [echo] ${x} > [echo] y > [echo] w > > You could also assign a value in the local-property, but using it as > above > allows setting the property using other tasks that set properties. > > The above is simple, and probably not too controversial, the > question is > what happens > if I do an <ant> or <antcall> within the <local-property/> which value > of ${x} should > be inherited in the call at that point of the execution? > > Such a task, would be not too dificult to do, but it really > needs access > to the > internals of ANT, it needs to be part of core, for sure. > > Jose Alberto > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
