2001-02-13 12:32:01 +00:00
|
|
|
<html>
|
|
|
|
|
|
|
|
<head>
|
|
|
|
<meta http-equiv="Content-Language" content="en-us">
|
2002-02-04 20:57:49 +00:00
|
|
|
<title>Directory-based Tasks</title>
|
2001-02-13 12:32:01 +00:00
|
|
|
</head>
|
|
|
|
|
|
|
|
<body>
|
|
|
|
|
|
|
|
<h2><a name="directorybasedtasks">Directory-based Tasks</a></h2>
|
2003-02-04 17:29:11 +00:00
|
|
|
<p>Some tasks use directory trees for the actions they perform.
|
|
|
|
For example, the <a href="CoreTasks/javac.html">javac</a> task, which
|
|
|
|
compiles a directory tree with <code>.java</code> files into
|
|
|
|
<code>.class</code> files, is one of these directory-based tasks. Because
|
|
|
|
some of these tasks do so much work with a directory tree, the task itself
|
|
|
|
can act as an implicit <a href="CoreTypes/fileset.html">FileSet</a>.</p>
|
|
|
|
<p>Whether the fileset is implicit or not, it can often be very useful to
|
|
|
|
work on a subset of the directory tree. This section describes how you can
|
|
|
|
select a subset of such a directory tree when using one of these
|
|
|
|
directory-based tasks.</p>
|
|
|
|
<p>Ant gives you two ways to create a subset of files in a fileset, both of
|
|
|
|
which can be used at the same time:</p>
|
2001-02-13 12:32:01 +00:00
|
|
|
<ul>
|
2003-02-04 17:29:11 +00:00
|
|
|
<li>Only include files and directories that match any
|
|
|
|
<code>include</code> patterns and do not match any
|
|
|
|
<code>exclude</code> patterns in a given
|
|
|
|
<a href="CoreTypes/patternset.html">PatternSet</a>.</li>
|
|
|
|
<li>Select files based on selection criteria defined by a collection of
|
|
|
|
<a href="CoreTypes/selectors.html">selector</a> nested elements.</li>
|
2001-02-13 12:32:01 +00:00
|
|
|
</ul>
|
2003-02-04 17:29:11 +00:00
|
|
|
<h3><a name="patternset">Patternset</a></h3>
|
|
|
|
|
|
|
|
<p>We said that Directory-based tasks can sometimes act as an implicit
|
|
|
|
<a href="CoreTypes/fileset.html"><code><fileset></code></a>,
|
|
|
|
but in addtion to that, a FileSet acts as an implicit
|
|
|
|
<a href="CoreTypes/patternset.html"><code><patternset></code></a>.</p>
|
|
|
|
|
|
|
|
<p>The inclusion and exclusion elements of the implicit PatternSet can be
|
|
|
|
specified inside the directory-based task (or explicit fileset) via
|
|
|
|
either:</p>
|
|
|
|
<ul>
|
|
|
|
<li>the attributes <code>includes</code> and
|
|
|
|
<code>excludes</code>.</li>
|
|
|
|
<li>nested elements <code><include></code> and
|
|
|
|
<code><exclude></code>.</li>
|
|
|
|
<li>external files specified with the attributes
|
|
|
|
<code>includesfile</code> and <code>excludesfile</code>.</li>
|
|
|
|
<li>external files specified with the nested elements
|
|
|
|
<code><includesfile></code> and <code><excludesfile></code>.
|
|
|
|
</li>
|
|
|
|
</ul>
|
|
|
|
When dealing with an external file, each line of the file
|
2002-02-03 01:53:34 +00:00
|
|
|
is taken as a pattern that is added to the list of include or exclude
|
2001-02-13 12:32:01 +00:00
|
|
|
patterns.</p>
|
2003-02-04 17:29:11 +00:00
|
|
|
|
|
|
|
<p>When both inclusion and exclusion are used, only files/directories that
|
|
|
|
match at least one of the include patterns and don't match any of the
|
|
|
|
exclude patterns are used. If no include pattern is given, all files
|
|
|
|
are assumed to match the include pattern (with the possible exception of
|
|
|
|
the default excludes).</p>
|
|
|
|
|
|
|
|
<h4><a name="patterns">Patterns</a></h4>
|
|
|
|
|
|
|
|
<p>As described earlier, patterns are used for the inclusion and exclusion
|
|
|
|
of files. These patterns look very much like the patterns used in DOS and
|
|
|
|
UNIX:</p>
|
2001-02-13 12:32:01 +00:00
|
|
|
<p>'*' matches zero or more characters, '?' matches one character.</p>
|
|
|
|
<p><b>Examples:</b></p>
|
|
|
|
<p>
|
|
|
|
<code>*.java</code> matches <code>.java</code>,
|
|
|
|
<code>x.java</code> and <code>FooBar.java</code>, but
|
|
|
|
not <code>FooBar.xml</code> (does not end with <code>.java</code>).</p>
|
|
|
|
<p>
|
|
|
|
<code>?.java</code> matches <code>x.java</code>,
|
|
|
|
<code>A.java</code>, but not <code>.java</code> or <code>xyz.java</code>
|
|
|
|
(both don't have one character before <code>.java</code>).</p>
|
|
|
|
<p>
|
|
|
|
Combinations of <code>*</code>'s and <code>?</code>'s are allowed.</p>
|
|
|
|
<p>Matching is done per-directory. This means that first the first directory in
|
|
|
|
the pattern is matched against the first directory in the path to match. Then
|
2003-02-04 17:29:11 +00:00
|
|
|
the second directory is matched, and so on. For example, when we have the pattern
|
|
|
|
<code>/?abc/*/*.java</code>
|
2001-02-13 12:32:01 +00:00
|
|
|
and the path <code>/xabc/foobar/test.java</code>,
|
|
|
|
the first <code>?abc</code> is matched with <code>xabc</code>,
|
|
|
|
then <code>*</code> is matched with <code>foobar</code>,
|
|
|
|
and finally <code>*.java</code> is matched with <code>test.java</code>.
|
|
|
|
They all match, so the path matches the pattern.</p>
|
|
|
|
<p>To make things a bit more flexible, we add one extra feature, which makes it
|
|
|
|
possible to match multiple directory levels. This can be used to match a
|
|
|
|
complete directory tree, or a file anywhere in the directory tree.
|
|
|
|
To do this, <code>**</code>
|
|
|
|
must be used as the name of a directory.
|
|
|
|
When <code>**</code> is used as the name of a
|
|
|
|
directory in the pattern, it matches zero or more directories.
|
|
|
|
For example:
|
|
|
|
<code>/test/**</code> matches all files/directories under <code>/test/</code>,
|
|
|
|
such as <code>/test/x.java</code>,
|
|
|
|
or <code>/test/foo/bar/xyz.html</code>, but not <code>/xyz.xml</code>.</p>
|
2001-03-09 08:54:35 +00:00
|
|
|
<p>There is one "shorthand" - if a pattern ends
|
2001-02-13 12:32:01 +00:00
|
|
|
with <code>/</code>
|
|
|
|
or <code>\</code>, then <code>**</code>
|
|
|
|
is appended.
|
|
|
|
For example, <code>mypackage/test/</code> is interpreted as if it were
|
|
|
|
<code>mypackage/test/**</code>.</p>
|
|
|
|
<p><b>Example patterns:</b></p>
|
|
|
|
<table border="1" cellpadding="2" cellspacing="0">
|
|
|
|
<tr>
|
|
|
|
<td valign="top"><code>**/CVS/*</code></td>
|
2003-02-04 17:29:11 +00:00
|
|
|
<td valign="top">Matches all files in <code>CVS</code>
|
|
|
|
directories that can be located
|
2001-02-13 12:32:01 +00:00
|
|
|
anywhere in the directory tree.<br>
|
|
|
|
Matches:
|
|
|
|
<pre>
|
|
|
|
CVS/Repository
|
|
|
|
org/apache/CVS/Entries
|
|
|
|
org/apache/jakarta/tools/ant/CVS/Entries
|
|
|
|
</pre>
|
|
|
|
But not:
|
|
|
|
<pre>
|
2003-02-04 17:29:11 +00:00
|
|
|
org/apache/CVS/foo/bar/Entries (<code>foo/bar/</code>
|
|
|
|
part does not match)</td>
|
2001-02-13 12:32:01 +00:00
|
|
|
</pre>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td valign="top"><code>org/apache/jakarta/**</code></td>
|
2003-02-04 17:29:11 +00:00
|
|
|
<td valign="top">Matches all files in the <code>org/apache/jakarta</code>
|
|
|
|
directory tree.<br>
|
2001-02-13 12:32:01 +00:00
|
|
|
Matches:
|
|
|
|
<pre>
|
|
|
|
org/apache/jakarta/tools/ant/docs/index.html
|
|
|
|
org/apache/jakarta/test.xml
|
|
|
|
</pre>
|
|
|
|
But not:
|
|
|
|
<pre>
|
|
|
|
org/apache/xyz.java
|
|
|
|
</pre>
|
|
|
|
(<code>jakarta/</code> part is missing).</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td valign="top"><code>org/apache/**/CVS/*</code></td>
|
|
|
|
<td valign="top">Matches all files in <code>CVS</code> directories
|
|
|
|
that are located anywhere in the directory tree under
|
|
|
|
<code>org/apache</code>.<br>
|
|
|
|
Matches:
|
|
|
|
<pre>
|
|
|
|
org/apache/CVS/Entries
|
|
|
|
org/apache/jakarta/tools/ant/CVS/Entries
|
|
|
|
</pre>
|
|
|
|
But not:
|
|
|
|
<pre>
|
|
|
|
org/apache/CVS/foo/bar/Entries
|
|
|
|
</pre>
|
|
|
|
(<code>foo/bar/</code> part does not match)</td>
|
|
|
|
</tr>
|
|
|
|
<tr>
|
|
|
|
<td valign="top"><code>**/test/**</code></td>
|
|
|
|
<td valign="top">Matches all files that have a <code>test</code>
|
|
|
|
element in their path, including <code>test</code> as a filename.</td>
|
|
|
|
</tr>
|
|
|
|
</table>
|
|
|
|
<p>When these patterns are used in inclusion and exclusion, you have a powerful
|
|
|
|
way to select just the files you want.</p>
|
|
|
|
|
2003-02-04 17:29:11 +00:00
|
|
|
<h3><a name="selectors">Selectors</a></h3>
|
|
|
|
<p>The <a href="CoreTypes/fileset.html"><code><fileset></code></a>,
|
|
|
|
whether implicit or explicit in the
|
|
|
|
directory-based task, also acts as an
|
|
|
|
<a href="CoreTypes/selectors.html#andselect"><code><and></code></a>
|
|
|
|
selector container. This can be used to create arbitrarily complicated
|
|
|
|
selection criteria for the files the task should work with. See the
|
|
|
|
<a href="CoreTypes/selectors.html">Selector</a> documentation for more
|
|
|
|
information.</p>
|
|
|
|
|
|
|
|
<h3><a name="tasklist">Standard Tasks/Filesets</a></h3>
|
|
|
|
<p>Many of the standard tasks in ant take one or more filesets which follow
|
|
|
|
the rules given here. This list, a subset of those, is a list of standard ant
|
|
|
|
tasks that can act as an implicit fileset:</p>
|
|
|
|
<ul>
|
|
|
|
<li><a href="CoreTasks/checksum.html"><checksum></a></li>
|
|
|
|
<li><a href="CoreTasks/copydir.html"><copydir></a> (deprecated)</li>
|
|
|
|
<li><a href="CoreTasks/delete.html"><delete></a></li>
|
|
|
|
<li><a href="CoreTasks/dependset.html"><dependset></a></li>
|
|
|
|
<li><a href="CoreTasks/fixcrlf.html"><fixcrlf></a></li>
|
|
|
|
<li><a href="CoreTasks/javac.html"><javac></a></li>
|
|
|
|
<li><a href="CoreTasks/replace.html"><replace></a></li>
|
|
|
|
<li><a href="CoreTasks/rmic.html"><rmic></a></li>
|
|
|
|
<li><a href="CoreTasks/style.html"><style> (aka <xslt>)</a></li>
|
|
|
|
<li><a href="CoreTasks/tar.html"><tar></a></li>
|
|
|
|
<li><a href="CoreTasks/zip.html"><zip></a></li>
|
|
|
|
<li><a href="OptionalTasks/ejb.html#ddcreator"><ddcreator></a></li>
|
|
|
|
<li><a href="OptionalTasks/ejb.html#ejbjar.html"><ejbjar></a></li>
|
|
|
|
<li><a href="OptionalTasks/ejb.html#ejbc"><ejbc></a></li>
|
|
|
|
<li><a href="OptionalTasks/cab.html"><cab></a></li>
|
|
|
|
<li><a href="OptionalTasks/icontract.html"><icontract></a></li>
|
|
|
|
<li><a href="OptionalTasks/native2ascii.html"><native2ascii></a></li>
|
|
|
|
<li><a href="OptionalTasks/netrexxc.html"><netrexxc></a></li>
|
|
|
|
<li>
|
|
|
|
<a href="OptionalTasks/renameextensions.html"><renameextensions></a>
|
|
|
|
</li>
|
|
|
|
<li><a href="OptionalTasks/depend.html"><depend></a></li>
|
|
|
|
<li><a href="OptionalTasks/dotnet.html"><ilasm></a></li>
|
|
|
|
<li><a href="OptionalTasks/dotnet.html"><csc></a></li>
|
|
|
|
<li><a href="OptionalTasks/dotnet.html"><vbc></a></li>
|
|
|
|
<li><a href="OptionalTasks/translate.html"><translate></a></li>
|
|
|
|
<li>
|
|
|
|
<a href="Integration/VAJAntTool.html#vajexport"><vajexport></a>
|
|
|
|
</li>
|
|
|
|
<li><image></li>
|
|
|
|
<li><a href="OptionalTasks/jlink.html"><jlink></a> (deprecated)</li>
|
|
|
|
<li><a href="OptionalTasks/jspc.html"><jspc></a></li>
|
|
|
|
<li><a href="OptionalTasks/wljspc.html"><wljspc></a></li>
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
<h3><a name="examples">Examples</a></h3>
|
2002-02-03 01:53:34 +00:00
|
|
|
<pre>
|
2001-09-08 01:05:18 +00:00
|
|
|
<copy todir="${dist}">
|
2002-02-03 01:53:34 +00:00
|
|
|
<fileset dir="${src}"
|
|
|
|
includes="**/images/*"
|
|
|
|
excludes="**/*.gif"
|
2001-02-13 12:32:01 +00:00
|
|
|
/>
|
|
|
|
</copy></pre>
|
|
|
|
<p>This copies all files in directories called <code>images</code> that are
|
|
|
|
located in the directory tree defined by <code>${src}</code> to the
|
|
|
|
destination directory defined by <code>${dist}</code>,
|
|
|
|
but excludes all <code>*.gif</code> files from the copy.</p>
|
|
|
|
<pre>
|
2001-09-08 01:05:18 +00:00
|
|
|
<copy todir="${dist}">
|
2001-07-20 14:01:48 +00:00
|
|
|
<fileset dir="${src}">
|
2001-02-13 12:32:01 +00:00
|
|
|
<include name="**/images/*"/>
|
|
|
|
<exclude name="**/*.gif"/>
|
|
|
|
</fileset>
|
|
|
|
</copy>
|
|
|
|
</pre>
|
2003-02-04 17:29:11 +00:00
|
|
|
<p> The same as the example above, but expressed using nested elements.</p>
|
|
|
|
|
|
|
|
<pre>
|
|
|
|
<delete dir="${dist}">
|
|
|
|
<include name="**/images/*"/>
|
|
|
|
<exclude name="**/*.gif"/>
|
|
|
|
</delete>
|
|
|
|
</pre>
|
|
|
|
<p>Deleting the original set of files, the <code>delete</code> task can act
|
|
|
|
as an implicit fileset.</p>
|
2001-02-13 12:32:01 +00:00
|
|
|
|
2001-11-21 16:29:49 +00:00
|
|
|
<h3><a name="defaultexcludes">Default Excludes</a></h3>
|
2003-02-04 17:29:11 +00:00
|
|
|
<p>There are a set of definitions that are excluded by default from all
|
|
|
|
directory-based tasks. They are:</p>
|
2001-02-13 12:32:01 +00:00
|
|
|
<pre>
|
|
|
|
**/*~
|
|
|
|
**/#*#
|
2001-03-29 10:29:46 +00:00
|
|
|
**/.#*
|
2001-02-13 12:32:01 +00:00
|
|
|
**/%*%
|
2002-02-03 01:53:34 +00:00
|
|
|
**/._*
|
2001-02-13 12:32:01 +00:00
|
|
|
**/CVS
|
|
|
|
**/CVS/**
|
|
|
|
**/.cvsignore
|
2001-03-29 10:29:46 +00:00
|
|
|
**/SCCS
|
|
|
|
**/SCCS/**
|
2001-07-12 13:02:47 +00:00
|
|
|
**/vssver.scc
|
2002-07-09 21:06:15 +00:00
|
|
|
**/.svn
|
|
|
|
**/.svn/**
|
2003-01-19 01:32:11 +00:00
|
|
|
**/.DS_Store
|
2001-02-13 12:32:01 +00:00
|
|
|
</pre>
|
2003-02-04 17:29:11 +00:00
|
|
|
<p>If you do not want these default excludes applied, you may disable them
|
|
|
|
with the <code>defaultexcludes="no"</code> attribute.</p>
|
2001-02-13 12:32:01 +00:00
|
|
|
<hr>
|
2003-02-04 17:29:11 +00:00
|
|
|
<p align="center">Copyright © 2000-2003 Apache Software Foundation. All
|
|
|
|
rights Reserved.</p>
|
2001-02-13 12:32:01 +00:00
|
|
|
|
|
|
|
</body>
|
|
|
|
</html>
|
|
|
|
|