>> But still, wouldn't it be nice for a Task implementor to have the 
>> possibility to turn off property replacement for some attributes? As 
>> long as it is documented it should be ok.
>
>makes things complex. how would we indicate it? Can't use 
>java5 attributes so that leaves the feared XML descriptor or a 
>new naming scheme for introspection, like noExpandsSetMyAttribute

class Task {
    Method[] getNotExpandableAttributes() { return null; }
}

But I think we would confuse Ant users if there are _some_ attributes
without replacements....



Jan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to