ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mben...@apache.org
Subject cvs commit: ant/docs/manual using.html
Date Wed, 25 May 2005 22:14:51 GMT
mbenson     2005/05/25 15:14:51

  Modified:    docs/manual using.html
  Log:
  Document ResourceCollections in paths.
  
  Revision  Changes    Path
  1.42      +13 -10    ant/docs/manual/using.html
  
  Index: using.html
  ===================================================================
  RCS file: /home/cvs/ant/docs/manual/using.html,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- using.html	29 Apr 2005 18:58:16 -0000	1.41
  +++ using.html	25 May 2005 22:14:51 -0000	1.42
  @@ -380,14 +380,16 @@
   <pre>
       &lt;classpath path=&quot;${classpath}&quot;/&gt;
   </pre>
  -<p>In addition, <a href="CoreTypes/dirset.html">DirSet</a>s,
  -<a href="CoreTypes/fileset.html">FileSet</a>s, and
  -<a href="CoreTypes/filelist.html">FileList</a>s
  -can be specified via nested <code>&lt;dirset&gt;</code>,
  -<code>&lt;fileset&gt;</code>, and <code>&lt;filelist&gt;</code>
  -elements, respectively. <em>Note</em>: The order in which the files
  -building up a FileSet are added to the path-like structure is not
  -defined.</p>
  +<p>In addition, one or more
  +<a href="CoreTypes/resources.html#collection">Resource Collection</a>s
  +can be specified as nested elements (these must consist of
  +<a href="CoreTypes/resources.html#file">file</a>-type resources only).
  +Additionally, it should be noted that although resource collections are
  +processed in the order encountered, certain resource collection types
  +such as <a href="CoreTypes/fileset.html">fileset</a>,
  +<a href="CoreTypes/dirset.html">dirset</a> and
  +<a href="CoreTypes/resources.html#files">files</a>
  +are undefined in terms of order.</p>
   <pre>
       &lt;classpath&gt;
         &lt;pathelement path=&quot;${classpath}&quot;/&gt;
  @@ -412,10 +414,11 @@
   <p>If you want to use the same path-like structure for several tasks,
   you can define them with a <code>&lt;path&gt;</code> element at the
   same level as <i>target</i>s, and reference them via their
  -<i>id</i> attribute - see <a href="#references">References</a>
for an
  +<i>id</i> attribute--see <a href="#references">References</a> for
an
   example.</p>
   <p>A path-like structure can include a reference to another path-like
  -structure via nested <code>&lt;path&gt;</code> elements:</p>
  +structure (a path being itself a resource collection)
  +via nested <code>&lt;path&gt;</code> elements:</p>
   <pre>
       &lt;path id=&quot;base.path&quot;&gt;
         &lt;pathelement path=&quot;${classpath}&quot;/&gt;
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message