Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 53489 invoked from network); 16 Dec 2001 11:38:04 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 16 Dec 2001 11:38:04 -0000 Received: (qmail 20982 invoked by uid 97); 16 Dec 2001 11:38:01 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 20966 invoked by uid 97); 16 Dec 2001 11:38:01 -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 20955 invoked from network); 16 Dec 2001 11:38:00 -0000 From: "Adam Murdoch" To: Subject: IntrospectionHelper questions Date: Sun, 16 Dec 2001 21:34:49 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, Some questions about IntrospectionHelper and friends. - IntrospectionHelper arbitrarily chooses an attribute setter method for a class when there is more than one of the same precedence. It silently ignores the others. Is there a reason for not failing, or at least writing a warning? Any problems with me adding a warning? Is an arbitrary choice of setter method really that useful? - Same sort of thing happens with 'create', 'add' and 'addConfigured'. What was the intention there? It looks like it was supposed to be choosing one of them, and ignoring the rest (it's not *quite* doing that). Any problems with a warning? Again, is arbitrary choice really that useful? - It looks like a refactor is overdue on the project parsing/construction/configuring side of things. With a bit of a tidy up, it should be a fair bit easier to add new features (e.g. the polymorphic datatypes idea that was raised a while back), improve existing features (e.g. a lightweight ), conditionally switch on experimental stuff (e.g. well, pretty much everything on the 1.9 action list), and reuse (e.g. for, say, loading up task lib descriptors from an XML file - or in Ant2). I realise, of course, that this stuff is the core of Ant, and that the whole backwards compatibility story depends heavily on it. So the question is, would there be any support for doing this? Exactly what "this" means, we can decide on later. I'm just trying to get a feel for what is fixed in stone, and what is fair game for tidy-up. Adam -- To unsubscribe, e-mail: For additional commands, e-mail: