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 71978 invoked from network); 31 Oct 2000 06:20:28 -0000 Received: from w002.z208176150.sjc-ca.dsl.cnc.net (HELO mail.x180.com) (208.176.150.2) by locus.apache.org with SMTP; 31 Oct 2000 06:20:28 -0000 Received: from [129.158.118.159] ([127.0.0.1]) by mail.x180.com (Netscape Messaging Server 4.15) with ESMTP id G3A6OL00.UKL for ; Mon, 30 Oct 2000 22:14:45 -0800 User-Agent: Microsoft-Entourage/9.0.2509 Date: Mon, 30 Oct 2000 22:18:16 -0800 Subject: Re: Role of scripts [was Re: increment task] From: "James Duncan Davidson" To: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On 10/27/00 9:37 AM, "Patrick Beard" wrote: > I suppose your being ironic here, I certainly intend to keep thinking > while I write build.xml files, although, I wouldn't be against using > an IDE tool to construct them (hallelujah). History Time: When I was looking at what build file format to use, XML wasn't my first choice. I actually used properties in an early version. Then I used something that was kind of like Jam. The reason for going with XML was that it seemed to capture the hierarchical structure that I wanted and that it was easy for tools to manipulate. Hand editing of build files should be something that isn't a primary case imho. -- James Duncan Davidson duncan@x180.com !try; do()