Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 1789 invoked from network); 15 Dec 2000 01:24:52 -0000 Received: from mail.alphalink.com.au (203.24.205.7) by locus.apache.org with SMTP; 15 Dec 2000 01:24:52 -0000 Received: from donalgar (d278-ps0-mel.alphalink.com.au [202.161.105.24]) by mail.alphalink.com.au (8.9.3/8.9.3) with SMTP id MAA14242; Fri, 15 Dec 2000 12:24:49 +1100 Message-Id: <3.0.6.32.20001215122208.00a1c100@latcs2.cs.latrobe.edu.au> X-Sender: pjdonald@latcs2.cs.latrobe.edu.au X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 15 Dec 2000 12:22:08 +1100 To: ant-dev@jakarta.apache.org From: Peter Donald Subject: RE: Anteater... I'm Baaaack... Cc: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N At 08:15 14/12/00 -0500, James Cook wrote: >I see round-tripping as a major impetus behind an Ant 2.0. I guess I have to >see a list of the shortcomings in Ant 1.2! I haven't experienced too many >from a user's perspective. The only real shortcomings from a users perspective I know of are * you have to use build scripts * task registration isn't as easy as it could be * classpath management is often painful However there are things that would be nice features - JPan discussed a while back is one of them as is the idea of "Workspaces" that contain many ant-projects. >I imagine that we should start to collect a list of these shortcomings so we >(you) know what needs to be addressed in a new version. I'll start: > >1. Ant build scripts should be parsed from a variety of valid input sources >into a DOM structure to facilitate Ant integration into GUI editing >environments. (let the flames begin) :-) W3C DOM will never get into core. Waaaaaay to much overhead. However some form of abstracted DOM would be useful. I proposed a Configuration object which is a 1-to-1 mapping with Ants idea of object model. AntEater presumably uses nested hashtables. Another good option is JDOM thou no one warmed up to that idea ;) Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------*