Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
Message-ID: <3B03EEFA.B88A603D@digitalfocus.com>
Date: Thu, 17 May 2001 11:32:10 -0400
From: Daniel Barclay <Daniel.Barclay@digitalfocus.com>
MIME-Version: 1.0
To: ant-dev@jakarta.apache.org
Subject: Re: if and unless attributes for all Tasks
References: <3B03A95D.23049.1E9ED8E1@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Michael McCallum wrote:
> 
> Why not use the script task?

Would one issue be that the ability to run a build file would depend 
on having the scripting framework and the particular script language 
installed?  (Compared to having <code...> and Java as a standard feature.)


Does the philosophy of Ant include trying to write build files using
standard features so Ant build files are more portable (e.g., so I 
can build some open-source system by processing that system's Ant 
build file using my Ant installation).

Or is the Ant philosphy that the system should come with a copy of 
Ant, with all add-ons (standard optional features and custom tasks, 
at least in source form) already included?


(I'm trying to understand this compared to make.  Make doesn't have
explicit add-ons, but of course any command you execute via a make
file could be and implicit add-on, something that the recipient doesn't 
already have and must add to his or her environment.)


Daniel
-- 
Daniel Barclay
Digital Focus
Daniel.Barclay@digitalfocus.com