ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Murdoch" <>
Subject RE: [myrmidon] configurer changes
Date Wed, 23 Jan 2002 00:27:47 GMT

> -----Original Message-----
> From: Peter Donald []
> Sent: Tuesday, 22 January 2002 10:23 PM
> To: Ant Developers List
> Subject: Re: [myrmidon] configurer changes
> > * Ignores String adder and setter methods, if other methods 
> exist.  Longer
> > term, the type should be able to specify exactly which method to use.
> Is this really needed? Hopefully in ant2 the contract will be at the XML 
> representation level and thus we should be able to change from 
> setFoo(String) 
> to setFoo(FooType) without breaking builds ... or so goes the theory - 
> thoughts?

This change was targeted at data-types, rather than tasks.  It is really just a stop-gap for
dealing with String convenience methods.  For example:

Path.addPath( String path )
Path.addPath( Path path )

I don't think we want to prevent classes doing this.  However, it would be good to let the
class have a say as to which overloaded method should be used by the configurer.  Maybe an
@ant:ignore tag on the methods that the introspector should ignore.

How do you see types (or other tasks, for that matter) being used programmatically in ant2?


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

View raw message