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 49255 invoked from network); 11 Dec 2000 02:20:03 -0000 Received: from marni.otago.ac.nz (root@139.80.75.248) by locus.apache.org with SMTP; 11 Dec 2000 02:20:03 -0000 Received: from localhost (mariusz@localhost) by marni.otago.ac.nz (8.9.3/8.9.3) with ESMTP id PAA29350 for ; Mon, 11 Dec 2000 15:20:02 +1300 Date: Mon, 11 Dec 2000 15:20:02 +1300 (NZDT) From: Mariusz Nowostawski To: ant-dev@jakarta.apache.org Subject: RE: [PROPOSAL] Optional Tasks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 11 Dec 2000, Conor MacNeill wrote: > How about: > > Core Tasks = all tasks ant needs to build itself. Just very quick look at ant build.xml and: replace, fail, exec-family, rename, ... and possibly others are not needed to build ant, but still, to me they _should_ be part of the core. The definition suggested is not good enough, I think. Personally, I also would like to have jikes support in core, whatever model of tasks ANT will have. No matter how nice the task pluggable architecture of ANT is, java compiler is a such integral part of every building process, that good support with variety of compilers is only good for ANT. If I could, I would discourage removing jikes from the core. ;o) cheers mariusz