We need you!

Icon

The IzPack documentation needs work, and you are invited to edit it!

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Current »

The FileSet Element

The IzPack fileset concept has been adapted from the Apache Ant FileSet core type. Its functionality has been shrunken to the needs of IzPack.

IzPack FileSets are groups of source files. These files can be found in a directory tree starting in a base directory and are matched by patterns taken from a number of Selectors. FileSets can appear as nested elements inside installation descriptors and the ConfigurationInstallerListener to describe groups of source files for their enclosing parent element.

FileSet supports the nested <include>, <includesfile>, <exclude> and <excludesfile> elements.

Selectors are available as nested elements.within the FileSet. If any of the selectors within the FileSet do not select the file, the file is not considered part of the FileSet. This makes FileSets equivalent to an <and> selector container.

Attribute

Description

Required

dir

The root of the directory tree of this FileSet

Either dir or file must be specified

file

Sshortcut for specifying a single file fileset.

Either dir or file must be specified

defaultexcludes

Indicates whether default excludes should be used or not (yes | no); default excludes are used when omitted.

No

includes

Comma- or space-separated list of patterns of files that must be included; all files are included when omitted.

No

includesfile

The name of a file; each line of this file is taken to be an include pattern.

No

excludes

Comma- or space-separated list of patterns of files that must be excluded; no files (except default excludes) are excluded when omitted

No

excludesfile

The name of a file; each line of this file is taken to be an exclude pattern.

No

casesensitive

Must the include and exclude patterns be treated in a case sensitive way? Defaults to true.

No

followsymlinks

Shall symbolic links be followed? Defaults to true. See the note below.

No

Note: All files/directories for which the canonical path is different from its path are considered symbolic links. On Unix systems this usually means the file really is a symbolic links but it may lead to false results on other platforms.

Examples

Groups all files in directory \${INSTALL_PATH} that are Java source files and don't have the text Test in their name.

Groups the same files as the previous example using a combination of the <filename> selector and the <not> selector container.

  • No labels