From ant-dev-return-23478-qmlist-jakarta-archive-ant-dev=jakarta.apache.org@jakarta.apache.org Wed Jan 23 11:06:19 2002 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 4880 invoked from network); 23 Jan 2002 11:06:19 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Jan 2002 11:06:19 -0000 Received: (qmail 6510 invoked by uid 97); 23 Jan 2002 11:05:23 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 6397 invoked by uid 97); 23 Jan 2002 11:05:20 -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 6189 invoked from network); 23 Jan 2002 11:05:16 -0000 Message-Id: <200201230915.g0N9FmR12326@mail004.syd.optusnet.com.au> Content-Type: text/plain; charset="utf-8" From: Peter Donald To: "Ant Developers List" Subject: Re: [VOTE] Ant2 codebase adoption process Date: Wed, 23 Jan 2002 20:04:43 +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 04:40, costinm@covalent.net wrote: > On Wed, 23 Jan 2002, Conor MacNeill wrote: > > The obvious candidates. IMHO are myrmidon and mutant. Other candidates > > may emerge in the discussion period. I do not believe we should include > > Ant 1.x as an option but again let us discuss. > > I think Ant1.x should be an option ( because that's what I would vote > for). > > I'm not an active ant commiter curently, but if my vote still counts > it'll be -1 on any candidate that doesn't have a clear backward > compatibility plan built into the design - i.e it should be able to run > most existing ant tasks and provide wrappers between the new APIs and > the old ones ( like xalan compat package for example ). It is actually realtively easy to get about 80-90% backwards compatability with most tasks. I actually had this working a while back till it broke gump builds - it wasn't really complete just a proof of concept. Hence it got zapped - should be easy to get that support back when we need it. However due to the relative porous nature of ant1.x it will be virtually impossible to support the remaining 10-20% because they directly reference things in ants core or use deprecated features and so forth. And with a somewhat complex XSLT sheet most ant build files will be able to be auotmagically migrated to ant2 or at least partially migrated. -- Cheers, Pete ---------------------------------- "Don't play dumb with me. I happen to be an expert at that" - Maxwell Smart ---------------------------------- -- To unsubscribe, e-mail: For additional commands, e-mail: