From 6b8d99e5f7b936efadd83e10fa398cea32c838c0 Mon Sep 17 00:00:00 2001
From: Matthew Jason Benson
/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 ... > @@ -554,14 +556,20 @@ example. </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.