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 82164 invoked from network); 2 Aug 2000 05:23:14 -0000 Received: from w002.z208176150.sjc-ca.dsl.cnc.net (HELO mail.x180.com) (208.176.150.2) by locus.apache.org with SMTP; 2 Aug 2000 05:23:13 -0000 Received: from [192.168.254.13] ([208.176.176.73]) by mail.x180.com (Netscape Messaging Server 4.15) with ESMTP id FYNG3X00.J49; Tue, 1 Aug 2000 22:19:09 -0700 User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Tue, 01 Aug 2000 22:21:04 -0700 Subject: Re: Utah From: "James Duncan Davidson" To: Eugen Kuleshov , Message-ID: In-Reply-To: <39875172.743918A6@home.com> 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 8/1/00 3:38 PM, Eugen Kuleshov at euxx@home.com wrote: > I've read your document whiteboard\utah\design guide.xml from current > Ant snapshot. There are great ideas. Actually, the Utah stuff is superceed by the "spec" document which is also in the repository. But thanks ! :) > But I have just small comment. How > about create DTD for build.xml file. It helps to validate build.xml > strucrure and make much simplier creating GUI tools for managing > build.xml By design, the build.xml file can't have a DTD that works in all case. The structure would have to change. There is a tool in the current distribution that lets you build a DTD from a set of tasks that will work. Most of the recent editors to come out are starting to acknowledge that XML has powerful uses that aren't 1:1 compatible with DTDs. For example, the new XMetal allows creating XML docs that don't have a DTD. In any case, please continue this conversation on the Ant-Dev mailing list. I don't really like having technical discussions on Ant outside of that forum. :) .duncan