Introduction

When the plugin is generating the prototype file it goes through the generatedPrototype list and expand any collection found into a set of files and any entry elements will be copied in directly. If a file is included twice the second declaration will override the first.

An "object collection" is similar to a resources element from Maven and a file set in the assembly plugin. It specifies object settings for any object that will be matched with the include/exclude settings. All include/exclude patterns are relative to the root of the package.

An "object entry" will result in a single line in the prototype file with the specified object.

If an "object collection" or an "object entry" doesn't specify a class, mode, user or group setting the default values will be used.

Collection Types

There are three kinds of collections:

• <directoryCollection> - generate "d" entries.
• <fileCollection> - generate "f" entries.
• <editableCollection> - generate "e" entries.

All the collection types have the same fields:

• <class> - sets the object class for the object.
• <mode> - sets the file mode for the object when installed.
• <user> and <group> - sets the file owner and group for the object.
• <includes> and <excludes> - sets the include/exclude patterns for the collection.

Entry Types

The following four entry types are supported:

• <directoryEntry> - generate "d" entries.
• <fileEntry> - generate "f" entries.
• <editableEntry> - generate "e" entries.
• <iEntry> - generate "i" entries.

All the entry types have the same fields:

• <class> - sets the object class for the object.
• <mode> - sets the file mode for the object when installed.
• <user> and <group> - sets the file owner and group for the object.
• <path> - sets the path to the object.
• <realPath> - sets the real path to the object. Useful when sucking in files from outside of the assembly area.