On Fri, 15 Oct 2004, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
> I just want to say that in my proposal, the temporary properties > only last for as long as the Project instance is executing. I know, still that might be too much. GridAnt is one such case, and I think there's been some kind of "incremental build" proposal that would rerun the same Project instance over and over again. Let's simply accept that people are doing weird things with Ant 8-) > How do you use <local/> in conjunction with <condition/>? > For this to work, you need a way to declare the property without > defining it, but shadowing any previous definition of such property. Exactly. That's what I had in mind. > As per my proposal, if the extended life of properties is considered > such a major issue, I am sure the implementation can be easily > changed to remove the property once the scope of the <let> i.e., > <macrodef/> is exited. It would certainly help me. > The reason I do not do it, is because <let/> does not define a > property, it just define a new name for one. And it is up to the > usage of our regular tasks to decide to define it or not. But notice > that one could use the name created by let, for anything else, not > just a property. I see - but it would need to get communicated back in order to be used outside of the macrodef's scope. > But we could add a way to say, "clean any property of this name on > macrodef exit", that would be quite easy to do, I think. And make it the default behaviour? Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
