From ant-dev-return-23476-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Wed Jan 23 11:06:03 2002 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 4614 invoked from network); 23 Jan 2002 11:06:03 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Jan 2002 11:06:03 -0000 Received: (qmail 6378 invoked by uid 97); 23 Jan 2002 11:05:19 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 6261 invoked by uid 97); 23 Jan 2002 11:05:18 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 6170 invoked from network); 23 Jan 2002 11:05:16 -0000 Message-Id: <200201230915.g0N9FkR12284@mail004.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Ant Developers List" Subject: Re: [myrmidon] configurer changes Date: Wed, 23 Jan 2002 18:52:39 +1100 X-Mailer: KMail [version 1.3.2] References: In-Reply-To: X-Wisdom-Cookie: . MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 23 Jan 2002 11:27, Adam Murdoch wrote: > > -----Original Message----- > > From: Peter Donald [mailto:peter@apache.org] > > 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 ) aahhh .. that makes sense. > 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. Thats an option. > How do you see types (or other tasks, for that matter) being used > programmatically in ant2? I don't really see tasks as being used programtically at all. As for "types" there are two sorts. First there are the adaptor/helper classes that are generally used to hold data and stuff (think Commandline object). Then there are types that are defined by an interface, gotten from the TypeManager and are extensible by the user (think Mappers, Conditions, Selectors etc). The adaptors need to either be stored in the framework or in the tasklibrary itself for task-loader reasons. The extensible types only need to have the interface in the base classloader and all the implementations can be in the task librarys. Thoughts? -- Cheers, Pete ---------------------------------------------------- "The only way to discover the limits of the possible is to go beyond them into the impossible." -Arthur C. Clarke ---------------------------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: