Return-Path: 
 <ant-dev-return-13570-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 97838 invoked by uid 500); 9 May 2001 09:52:26 -0000
Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
list-help: <mailto:ant-dev-help@jakarta.apache.org>
list-unsubscribe: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
list-post: <mailto:ant-dev@jakarta.apache.org>
Delivered-To: mailing list ant-dev@jakarta.apache.org
Received: (qmail 97280 invoked from network); 9 May 2001 09:52:15 -0000
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: ant-dev@jakarta.apache.org
Subject: Re: Peter's ANT2 design proposals
References: 
 <59B1C000C017D411A43200508BC7494E6CDA5E@statistics.portal.hoteltools.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: 09 May 2001 11:52:22 +0200
In-Reply-To: Jesse Tilly's message of "Tue, 8 May 2001 14:27:19 -0400"
Message-ID: <m3g0eealyh.fsf@bodewig.bost.de>
Lines: 34
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Jesse Tilly <JTilly@hoteltools.com> wrote:

> People simply put:
> 
> <app>
>   <jar><package/></jar>
>   <package/>
> </app>
> 
> To build a jar and an open class package.  Transforms and rulesets
> define what will really happen under the covers.

You could already write XSLT to do something like this, or a velocity
style or a Perl script.  All you are asking for is a front end to Ant
- that could invoke Ant under the cover - not for a change of Ant
itself.  Or am I missing something.

> Ant1 files and one for Ant2 raw files.  This would [...]  users to
> upgrade without ditching 3-10 months worth of antfiles.

I'm not that concerned about ditching old ant files as we will
certainly provide a tool that converts Ant files to a similar Ant2
version or a separate front end for Ant2 that performs this conversion
implicitly.

Ditching 3-10 months worth of custom tasks may be a much stronger
argument IMHO, and we need to account for this in some way as well.

> Ok, that breaks the Ant2 goal of breaking Ant1,

Breaking Ant1 compatibility is not a goal of Ant2, but a result of
other goals.

Stefan