On Thu, 13 Sep 2001 00:31, Kyle Adams wrote: > > Why can't you grab this from the listener interface? (Which is the > > recomended way of doing this sorta stuff). > > I could, but it seemed inconsistent that Ant has an internal property > defining the project name (ant.project.name), but no internal property to > define the target name (ant.target.name). I felt the patch addressed an > inconsistency in Ant's design (albeit a minor one).
I have lobbied (unsucessfully) to remove that inconsistancy by removing the ant.project.name property ;) Feel free to throw in your support for that move ;) > > Most people who ask for it want it so that they can implement dynamic > > templating. > > I'm not sure I follow you here. Dynamic templating how? I guess I've > always associated dynamic templating with XSLT, probably because that's the > way I do it :-) The more I think about it the more I like XSLT for this but many people disagree and believe ant should natively have mutable properties, forall/foreach tasks, if tasks, return values from targets ... etc. Ie they believe that ant should become a scripting language ;) -- Cheers, Pete ------------------------------------------ I just hate 'yes' men, don't you Smithers? ------------------------------------------
