On Fri, 3 Aug 2001, Peter Donald <[EMAIL PROTECTED]> wrote:

> On Fri,  3 Aug 2001 15:26, Stefan Bodewig wrote:
>>
>> We already have built-in tasks that have attributes and nested
>> elements of the same name (see javac with classpath).  Tasks may
>> have chosen to do different things with them (javac does, but this
>> is silly).
> 
> but they are still differentiable .. you said so as much below ;)

I did?

If the method for nested <classpath> elements in <javac> becomes
setClasspath(Path), how can it be distinguished from the attribute
setter?

Maybe you are advocation Path[] as the argument for setters of nested
elements?

Stefan

Reply via email to