Return-Path: 
 <ant-dev-return-11858-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org
Received: (qmail 49475 invoked by uid 500); 23 Mar 2001 11:51:04 -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 49379 invoked from network); 23 Mar 2001 11:51:02 -0000
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@bost.de using -f
To: ant-dev@jakarta.apache.org
Subject: Re: [ANN] Collecting requirements for Ant2
References: <001d01c0b2f7$20eec8c0$3f28e9ce@eidea.com>
From: Marvin Greenberg (marvin.greenberg@acm.org via Stefan Bodewig)
 <bodewig@apache.org>
Date: 23 Mar 2001 12:51:00 +0100
Message-ID: <m3d7b8snyz.fsf@bodewig.bost.de>
Lines: 48
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

I haven't said anything for a while and mostly you have no idea who I
am but I'll jump in anyway.  The procedural vs. declarative argument
is a fallacy.  As has been pointed out, a procedure is a declaration.
The important point (IMHO) is that the declaration in the build tool
should declare as clearly as possible the intent of the CM
person/build manager etc.

Some amount of stuff like foreach etc... might be OK (although my
prejudices/beliefs are to avoid it) because it can be useful and some
people will use it for complex unanticipated situations.  I think Ant
should try to push it to the edges though.  The example way below can
be expressed:

<dirlist refid="toolkitdirs"  include="toolkit/*" />

<complextask name=build>
   <task name=compile />
   <task name=jar requires=compile />
</complextask>

<task name=build dirlist="toolkitdirs">

Now this is a bit of hand waving and not totally clear.  I have told
Stefan I will put together something RSN to describe some of the ideas
I've come across, from the workflow and process definition world.  Ant
is defining a build process, and there is a lot of literature and
previous work about how to express a process.  Tasks have subtasks,
input and outputs, constraints, dependencies. (Unfortunately I'm
totally swamped at my job that I've resigned from, and am still
struggling with the implications of a non-compete agreement and trying
to be professional and leave with a successful completion of my
current project, so you should all feel sorrry for me.  ;-) (P.S.  I
really like Ant and 15 years of 'make' is enough.))

Marvin

At 10:45  21/3/01 +1100, Tim Vernum wrote:

>>I think that the desire to do something like
>>
>> Foreach subdir in toolkit
>> do
>> Compile subdir/source to subdir/classes
>> Jar subdir/classes to subdir/subdir.jar
>> done
>>
>>is a valid request for a build tool, and I don't see it as
>>being declarative.