On Fri, 10 Sep 2004, Ian MacLean <[EMAIL PROTECTED]> wrote: > I was under the impression that Ant properties also have global > scope but maybe this has changed recently.
They are. > If this is still true then I wonder how the parallel task in Ant > works around it. It doesn't, really. But then again you are very unlikely to face the problem in Ant. <parallel> takes nested tasks in Ant. The only "regular" tasks in Ant that execute targets will create new build contexts (<ant>, <antcall> and friends) and those inherit the current properties, but any property created inside this context is invisible to the spawning context as well as to sibling contexts. There are tasks that run different targets inside the same build context outside of Ant's core and thus would exhibit the problem Andy faces. But these tasks are rarely used. We've been playing with scoped properties in Ant in context with <macrodef>[1] and we probably would use ThreadLocal stores for those scoped properties. Stefan Footnotes: [1] part of the reasons is captured in <http://www.oracle.com/technology/pub/articles/bodewig_ant1.6.html> if you are really interested. ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
