On 2009-09-01, Matt Benson wrote:
> Note that the props antlib does provide a NestedPropertyExpander, so
> you're right on track.
Thanks, I've modified the documentation to link to it.
> The NullReturn thing, IIRC, was added by Peter.
Now documented explicitly.
Thanks for checking
Ste
Yes, I think that I added the null return to allow local properties.
Peter
On Tue, Sep 1, 2009 at 1:08 PM, Matt Benson wrote:
>
>
> --- On Tue, 9/1/09, Stefan Bodewig wrote:
>
>> From: Stefan Bodewig
>> Subject: PropertyHelper API
>> To: dev@ant.apache.org
>&
On Tue, Sep 1, 2009 at 9:42 AM, Stefan Bodewig wrote:
> On 2009-09-01, Dominique Devienne wrote:
>
>> What I don't get is how NestedPropertyExpander can be enabled.
>> Given how DEFAULT_EXPANDER works, if one tries to add
>> NestedPropertyExpander after it, the first expander will not allow
>> the
On 2009-09-01, Dominique Devienne wrote:
> What I don't get is how NestedPropertyExpander can be enabled.
> Given how DEFAULT_EXPANDER works, if one tries to add
> NestedPropertyExpander after it, the first expander will not allow
> the second to work.
You missed the "delegates get used in LIFO
On Tue, Sep 1, 2009 at 7:08 AM, Matt Benson wrote:
>> From: Stefan Bodewig
>> wanted to allow nested properties ${${foo}} since the default
>> PropertyExpander doesn't balance braces.
>
> Note that the props antlib does provide a NestedPropertyExpander, so you're
> right on track.
pr
--- On Tue, 9/1/09, Stefan Bodewig wrote:
> From: Stefan Bodewig
> Subject: PropertyHelper API
> To: dev@ant.apache.org
> Date: Tuesday, September 1, 2009, 4:59 AM
> Hi
>
> I'm trying to grok the changes to the PropertyHelper in
> order to
> document them
Hi
I'm trying to grok the changes to the PropertyHelper in order to
document them for 1.8.0 - and maybe to suggest throwing in some more
built-in delegates, but that's for a different thread.
>From what I understand:
The default PropertyHelper splits its work into several steps that can
be deleg
