Return-Path: 
 <ant-dev-return-11351-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 10934 invoked by uid 500); 12 Mar 2001 20:05:00 -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 10913 invoked from network); 12 Mar 2001 20:04:58 -0000
From: "Rosen, Alex" <arosen@silverstream.com>
To: ant-dev@jakarta.apache.org
Subject: RE: Ant 2.0 proposed requirements
Date: Mon, 12 Mar 2001 15:01:25 -0500
Message-ID: <003601c0ab2f$38db4280$2f65810a@silverstream.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
In-Reply-To: <m31ys377u5.fsf@bodewig.bost.de>
Importance: Normal
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N


> > (2) Key methods which provide base services should be publicly
> > accessible.
>
> Do you think
> >> * provide utility classes to aid in building tasks.
> covers this?

Probably.

Regarding numbers 4 and 5: I'm making a lot of this up on the fly, but I'm
trying to request that Ant be able to support the kinds of scripting that
people seem to want to do. The <script> example in the Ant doc shows writing
JavaScript code to perform a task, but what I think you'd really like is to be
able to include the normal XML of a task inside the script. So the example in
the doc would be (very roughly) something like:

<for "i=1; i<=10; i++">
	<echo message="i * i">
</for>

or perhaps

<for var="i" start="1" end="10">
	<echo message="${i} * ${i}">
</for>

So what this needs above the current <script> task is the ability to have
embedded tasks as XML elements, and what this needs above the "simple flow
control" is variables and expression evalutation.

Take this with a grain of salt, as I'm not very experienced with scripting
languages.

--Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org