Return-Path:
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 79622 invoked from network); 27 Jan 2005 17:52:17 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur-2.apache.org with SMTP; 27 Jan 2005 17:52:17 -0000
Received: (qmail 58576 invoked by uid 500); 27 Jan 2005 17:52:13 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 58484 invoked by uid 500); 27 Jan 2005 17:52:12 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe:
List-Subscribe:
List-Help:
List-Post:
List-Id: "Ant Developers List"
Reply-To: "Ant Developers List"
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 58433 invoked by uid 500); 27 Jan 2005 17:52:11 -0000
Received: (qmail 58406 invoked by uid 99); 27 Jan 2005 17:52:11 -0000
X-ASF-Spam-Status: No, hits=-9.8 required=10.0
tests=ALL_TRUSTED,NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from minotaur.apache.org (HELO minotaur.apache.org)
(209.237.227.194)
by apache.org (qpsmtpd/0.28) with SMTP; Thu, 27 Jan 2005 09:52:10 -0800
Received: (qmail 79428 invoked by uid 1818); 27 Jan 2005 17:52:08 -0000
Date: 27 Jan 2005 17:52:08 -0000
Message-ID: <20050127175208.79427.qmail@minotaur.apache.org>
From: mbenson@apache.org
To: ant-cvs@apache.org
Subject: cvs commit: ant/docs/manual using.html
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N
mbenson 2005/01/27 09:52:08
Modified: docs/manual Tag: ANT_16_BRANCH using.html
Log:
merge
PR: 33274
Revision Changes Path
No revision
No revision
1.31.2.6 +19 -11 ant/docs/manual/using.html
Index: using.html
===================================================================
RCS file: /home/cvs/ant/docs/manual/using.html,v
retrieving revision 1.31.2.5
retrieving revision 1.31.2.6
diff -u -r1.31.2.5 -r1.31.2.6
--- using.html 16 Dec 2004 16:24:57 -0000 1.31.2.5
+++ using.html 27 Jan 2005 17:52:08 -0000 1.31.2.6
@@ -504,11 +504,13 @@
/dir:/dir2:/dir3
on Unix-like systems.
-The id
attribute of the buildfile's elements can be
-used to refer to them. This can be useful if you are going to replicate
-the same snippet of XML over and over again - using a
-<classpath>
structure more than once, for
-example.
+
+Any project element can be assigned an identifier using its
+id
attribute. In most cases the element can subsequently
+be referenced by specifying the refid
attribute on an
+element of the same type. This can be useful if you are going to
+replicate the same snippet of XML over and over again--using a
+<classpath>
structure more than once, for example.
The following example:
<project ... >
@@ -555,14 +557,20 @@
</target>
</project>
-All tasks that use nested elements for PatternSets, FileSets,
-ZipFileSets or
-path-like structures accept references to these
-structures as well.
+All tasks that use nested elements for
+PatternSets,
+FileSets,
+ZipFileSets or
+path-like structures accept references to these structures
+as shown in the examples. Using refid
on a task will ordinarily
+have the same effect (referencing a task already declared), but the user
+should be aware that the interpretation of this attribute is dependent on the
+implementation of the element upon which it is specified. Some tasks (the
+property task is a handy example)
+deliberately assign a different meaning to refid
.
-Copyright © 2000-2004 The Apache Software Foundation. All rights
+
Copyright © 2000-2005 The Apache Software Foundation. All rights
Reserved.