|
> 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).
> 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 :-)
Thanks,
Kyle
|
- Re: on *evil practices* Alejandro Abdelnur
- howTo call an external process detlef . brendle
- RE: howTo call an external pr... Ingmar Stein
- Re: howTo call an external pr... Stefan Bodewig
- Re: on *evil practices* Peter Donald
- Re: on *evil practices* Alejandro Abdelnur
- Re: [PATCH] Added "ant.target.name" property Kyle Adams
- Ant include Ian MacLean
- Re: Ant include Stefan Bodewig
- Re: [PATCH] Added "ant.target.name" prop... Peter Donald
- Re: [PATCH] Added "ant.target.name" property Kyle Adams
- Re: [PATCH] Added "ant.target.name" prop... Peter Donald
- Re: [PATCH] Added "ant.target.name" property Stefano Mancarella
- Re: [PATCH] Added "ant.target.name" prop... Peter Donald
- Re: [PATCH] Added "ant.target.name" ... Peter Janes
- Re: [PATCH] Added "ant.target.name&qu... Peter Donald
- Re: [PATCH] Added "ant.target.name&qu... Matthew Inger
- Re: [PATCH] Added "ant.target.name" ... Stefan Bodewig
- Re: [PATCH] Added "ant.target.name" property Kyle Adams
