From b3fcc74e6a800bb5d72f07b45ce64a001771a984 Mon Sep 17 00:00:00 2001
From: Diane Holt FileLists are explicitly named lists of files. Whereas FileSets
act as filters, returning only those files that exist in the file
-system and match specified patterns, filelists are useful for
-specifying filenames that may or may not exist. Multiple files are
-specified via a comma-separated list, with no support for wildcards.
+system and match specified patterns, FileLists are useful for
+specifying files that may or may not exist. Multiple files are
+specified as a list of files, relative to the specified directory,
+with no support for wildcard expansion (filenames with wildcards will be
+included in the list unchanged).
FileLists can appear inside tasks that support this feature or at the
-same level as target
- i.e., as children of
-project
.
+same level as <target>
(i.e., as children of
+<project>
).
@@ -49,6 +51,16 @@ same level as
@@ -26,12 +28,12 @@ same level as
target
- i.e., as children of
dir
- the base directory of this FileList.
+ The base directory of this FileList.
Yes
files
- Comma-separated list of file names.
+ The list of file names.
Yes
target
- i.e., as children of
actually exist.
+ ++<filelist + id="docfiles" + dir="${doc.src}" + files="foo.xml + bar.xml"/> +
Same files as the example above.
+<filelist refid="docfiles"/>