ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: Possible Ant 1.7 alpha bug: property expansion.
Date Thu, 03 Jun 2004 14:48:36 GMT
--- Stefan Bodewig <> wrote:
> On Thu, 3 Jun 2004, Jose Alberto Fernandez
> <>
> wrote:
> > Agree in principle. As a matter of fact, we
> already have the
> > PropertyHelper chain framework.
> That's what I've been talking about, yes 8-)

Nice... however, since we're actually talking about
the parsing of properties from a String, we've got to
head 'em off at the pass, so to speak... meaning that
we can't use chaining at its simplest for this.  From
what I can tell by a quick look at the code, the main
ant.PropertyHelper reference should be set to the
recursion-aware PropertyHelper implementation.

So it should be possible to do:

<taskdef name="myph" classname="my.PropertyHelper" />
<myph id="ant.PropertyHelper" />


But setting the root PropertyHelper, especially given
the fact that a reference can be overwritten at any
time during the build, doesn't feel like it wants to
play nicely with chained PropertyHelpers.  Can anybody
think of a cool way (i.e. without using an
intermediate reference) for the newly instantiated
custom PropertyHelper to get a reference to the
current ant.PropertyHelper, in order to set it, or
maybe just its next node, to the next node of the
custom PropertyHelper?

We could create a new property
ant.PropertyHelper.classname or some such, to allow
users a comfortable way to avoid the situation above,
but AFAICT the issue still exists.


Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger. 

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message