RE: documenting your build file

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 98507 invoked from network); 19 Oct 2000 18:08:56 -0000 Received: from brick.eb.com (HELO CHIEC01.eb.com) (208.154.71.2) by locus.apache.org with SMTP; 19 Oct 2000 18:08:56 -0000 Received: by chiec01.eb.com with Internet Mail Service (5.5.2650.21) id ; Thu, 19 Oct 2000 13:08:24 -0500 Message-ID: <4538F96A1478D211BEC40008C7A4CD9D059CF8C4@chiec01.eb.com> From: rwaldhof@us.britannica.com To: ant-dev@jakarta.apache.org Subject: RE: documenting your build file Date: Thu, 19 Oct 2000 13:08:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C039F7.924D51E0" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C039F7.924D51E0 Content-Type: text/plain; charset="iso-8859-1" I'll second that. -----Original Message----- From: John Kohler [mailto:jkohler@daforma.com] Sent: Thursday, October 19, 2000 10:54 AM To: 'ant-dev@jakarta.apache.org' Subject: RE: documenting your build file I would recommend using namespaces. (If the build.xml does not now use a namespace, it would be a very good Idea to add it.) some description goes here ... ... The Ant parser would simply ignore any tags not in its own namespace. If you do this with namespaces, then ANY XML language (eg. XLink, RDF) could be embedded within the build files. ------_=_NextPart_001_01C039F7.924D51E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: documenting your build file

I'll second that.

-----Original Message-----
From: John Kohler [mailto:jkohler@daforma.com]
Sent: Thursday, October 19, 2000 10:54 AM
To: 'ant-dev@jakarta.apache.org'
Subject: RE: documenting your build file

I would recommend using namespaces. (If the = build.xml does not now
use a namespace, it would be a very good Idea to add = it.)

<target name=3D"init">
    <doc:descr>some description = goes here</doc:descr>
    <tstamp/>
    ...
</target>

...

The Ant parser would simply ignore any tags not in = its
own namespace. If you do this with namespaces, = then ANY
XML language (eg. XLink, RDF) could be embedded = within
the build files.

------_=_NextPart_001_01C039F7.924D51E0--