ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Levy Lambert <>
Subject Re: task that allows augmentation of previously declared references
Date Wed, 03 Mar 2010 21:13:47 GMT

I was thinking that ant datatypes are currently de-facto mutable by 
default. Maybe we are making this too complex.
Of course, only users who can write custom tasks in java or 
javascript/groovy/... can for instance add an include pattern to an 
existing fileset, but there is nothing preventing them from doing it.


Gilles Scokart wrote:
> I just have an idea that come into my mind.  I will quickly post it (and
> probably think it's stupid tomorow morning).
> Instead of a special id, we could maybe use a decorator :
> <mutabletype id="x">
>      <path ... />
> </mutabletype>
> Probably stupid, certainly not trivial to implement, but make it obvious
> that's a quiet special structure that should be used carrefully.
> Gilles Scokart
> On 3 March 2010 05:52, Stefan Bodewig <> wrote:
>> On 2010-03-02, Matt Benson <> wrote:
>>> Okay, let's reason this out... since tasks and types are Java objects
>>> can we assume that a Java property "final" is unlikely enough to be
>>> used that we can use it as a configuration "attribute"?
>> Agreed.  An alternative could be anything that contains a dash or any
>> other character that would be illegal in a Java method name (so you
>> can't have a set-method for it).
>>> Now, any id'd item would declare final=false if it wanted to be
>>> augmentable.  This would require changes in the way we handle
>>> references, but would seem doable.
>> +1
>> Stefan

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

View raw message