Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 23676 invoked from network); 10 Jul 2002 06:27:52 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Jul 2002 06:27:52 -0000 Received: (qmail 19760 invoked by uid 97); 10 Jul 2002 06:28:12 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 19736 invoked by uid 97); 10 Jul 2002 06:28:11 -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 19724 invoked by uid 98); 10 Jul 2002 06:28:11 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <00a101c227da$d4c80fb0$0100a8c0@jose> From: "Jose Alberto Fernandez" To: "Ant Developers List" References: Subject: Re: Ant 2 et al. Date: Wed, 10 Jul 2002 07:27:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N From: > On Tue, 9 Jul 2002, Conor MacNeill wrote: >=20 >=20 >=20 > Of course, any proposal needs to start by saying that whatever was > before is broken and can never be fixed. Most revolutions I know > are far for perfect, and some were far worse than what it was > before ( I'm thinking about general history here, not jakarta :-) >=20 > I still have to see one real issue that can't be resolved by=20 > the current codebase but can be by a proposal.=20 >=20 The main issue to me, and I am not completely sure it is fixed in the = proposals, is the ClassLoaders mess that we have today. With the current policy = that=20 every badly written task that works today must continue to work in the = future there is little posibility to fix this problem. A problem that otherwise = is completely fixable in Ant1, there has been several patches that did it. The other issue is to be able to separate better the execution engine so = that it can be reuse in projects that want a way to do things like compile files or perform = FTP, etc. without requiring firing a complete ANT build-project. Jose Alberto -- To unsubscribe, e-mail: For additional commands, e-mail: