From f03354ed8321376da7cd15f038bbe59a2b4e67d0 Mon Sep 17 00:00:00 2001 From: Matthew Jason Benson Date: Wed, 25 May 2005 22:14:51 +0000 Subject: [PATCH] Document ResourceCollections in paths. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@278361 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/using.html | 23 +++++++++++++---------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/docs/manual/using.html b/docs/manual/using.html index 9996473a4..5d8b8c85a 100644 --- a/docs/manual/using.html +++ b/docs/manual/using.html @@ -380,14 +380,16 @@ supports path and 
     <classpath path="${classpath}"/>
-

In addition, DirSets, -FileSets, and -FileLists -can be specified via nested <dirset>, -<fileset>, and <filelist> -elements, respectively. Note: The order in which the files -building up a FileSet are added to the path-like structure is not -defined.

+

In addition, one or more +Resource Collections +can be specified as nested elements (these must consist of +file-type resources only). +Additionally, it should be noted that although resource collections are +processed in the order encountered, certain resource collection types +such as fileset, +dirset and +files +are undefined in terms of order.

     <classpath>
       <pathelement path="${classpath}"/>
@@ -412,10 +414,11 @@ the files specified in the referenced FileList.

 
If you want to use the same path-like structure for several tasks,
 you can define them with a <path> element at the
 same level as targets, and reference them via their
-id attribute - see References for an
+id attribute--see References for an
 example.

 
A path-like structure can include a reference to another path-like
-structure via nested <path> elements:

+structure (a path being itself a resource collection)
+via nested <path> elements:

 
     <path id="base.path">
       <pathelement path="${classpath}"/>