Full name:
org.apache.jackrabbit:filevault-package-maven-plugin:1.1.1-SNAPSHOT:validate-files
Description:
Attributes:
| Name | Type | Since | Description |
|---|---|---|---|
| <excludes> | String[] | - | The file name patterns to exclude in addition to the ones listed in
AbstractScanner.DEFAULTEXCLUDES. The format of each
pattern is described in DirectoryScanner. The
comparison is against the path relative to the according filter
root. Since this is hardly predictable it is recommended to use
only filename/directory name patterns here but not take into
account file system hierarchies!
Each value is either a regex pattern if enclosed within %regex[ and ], otherwise an Ant pattern. Default value is: **/.vlt,**/.vltignore. User property is: vault.excludes. |
| <failOnDependencyErrors> | boolean | - | Deprecated. Use validatorsSettings with the following values
instead
<jackrabbit-dependencies>
<defaultSeverity>debug</defaultSeverity>
</jackrabbit-dependencies>
Default value is: true. User property is: vault.failOnDependencyErrors. |
| <jcrRootSourceDirectory> | File[] | - | The directory that contains the jcr_root of the content. Multiple
directories can be specified as a comma separated list, which will
act as a search path and cause the plugin to look for the first
existing directory. Default value is: ${project.basedir}/jcr_root,${project.basedir}/src/main/jcr_root,${project.basedir}/src/main/content/jcr_root,${project.basedir}/src/content/jcr_root,${project.build.outputDirectory}. User property is: vault.jcrRootSourceDirectory. |
| <metaInfVaultDirectory> | File[] | - | The directory that contains the META-INF/vault. Multiple
directories can be specified as a comma separated list, which will
act as a search path and cause the plugin to look for the first
existing directory.
This directory is added as fileset to the package archiver before the the workDirectory. This means that files specified in this directory have precedence over the one present in the workDirectory. For example, if this directory contains a properties.xml it will not be overwritten by the generated one. A special case is the filter.xml which will be merged with inline filters if present. Default value is: ${project.basedir}/META-INF/vault,${project.basedir}/src/main/META-INF/vault,${project.basedir}/src/main/content/META-INF/vault,${project.basedir}/src/content/META-INF/vault. User property is: vault.metaInfVaultDirectory. |
| <skipValidation> | boolean | - | (no description) Default value is: false. User property is: vault.skipValidation. |
| <workDirectory> | File | - | The directory containing the metadata to be packaged up into the
content package. Basically containing all files/folders being
generated by goal "generate-metadata". Default value is: ${project.build.directory}/vault-work. |
| Name | Type | Since | Description |
|---|---|---|---|
| <builtContentDirectory> | File | - | The directory containing the content to be packaged up into the
content package. This property is deprecated; use
jcrRootSourceDirectory instead. |
| <dependencies> | Collection | - | Defines the list of dependencies A dependency is declared as a
<dependency> element of a list style
<dependencies> element:
<dependency>
<group>theGroup</group>
<name>theName</name>
<version>1.5</version>
</dependency>
The dependency can also reference a maven project dependency, this is preferred as it yields to more robust builds.
<dependency>
<groupId>theGroup</groupId>
<artifactId>theName</artifactId>
</dependency>
The versionRange may be indicated as a single version, in which case the version range has no upper bound and defines the minimal version accepted. Otherwise, the version range defines a lower and upper bound of accepted versions, where the bounds are either included using parentheses () or excluded using brackets [] User property is: vault.dependencies. |
| <failOnValidationWarnings> | boolean | - | If set to true will lead to all validation errors or
warnings failing the build, otherwise only validation errors lead
to a build failure Default value is: false. User property is: vault.failOnValidationWarning. |
| <mapPackageDependencyToMavenGa> | Collection | - | Mapping of package dependencies given via group and name to Maven
identifiers for enhanced validation. Each entry must have the
format
<group>:<name>=<groupId>:<artifactId> User property is: vault.package.dependency.to.maven.ga. |
| <repositoryStructurePackages> | Collection | - | Defines the packages that define the repository structure. For the
format description look at dependencies.
The repository-init feature of sling-start can define initial content that will be available in the repository before the first package is installed. Packages that depend on those nodes have no way to reference any dependency package that provides these nodes. A "real" package that would creates those nodes cannot be installed in the repository, because it would void the repository init structure. On the other hand would filevault complain, if the package was listed as dependency but not installed in the repository. So therefore this repository-structure packages serve as indicator packages that helps satisfy the structural dependencies, but are not added as real dependencies to the package. User property is: vault.repository.structure.packages. |
| <validatorsSettings> | Map | - | All validator settings in a map. The keys are the validator ids and
the values are a complex object of type ValdidatorSettings. An
example configuration looks like
<jackrabbit-filter>
<options>
<
</options>
</jackrabbit-filter>
|
<dependency>
<group>theGroup</group>
<name>theName</name>
<version>1.5</version>
</dependency>
The dependency can also reference a maven project dependency, this is preferred as it yields to more robust builds.
<dependency>
<groupId>theGroup</groupId>
<artifactId>theName</artifactId>
</dependency>
The versionRange may be indicated as a single version, in which case the version range has no upper bound and defines the minimal version accepted. Otherwise, the version range defines a lower and upper bound of accepted versions, where the bounds are either included using parentheses () or excluded using brackets []
Each value is either a regex pattern if enclosed within %regex[ and ], otherwise an Ant pattern.
<jackrabbit-dependencies>
<defaultSeverity>debug</defaultSeverity>
</jackrabbit-dependencies>
This directory is added as fileset to the package archiver before the the workDirectory. This means that files specified in this directory have precedence over the one present in the workDirectory. For example, if this directory contains a properties.xml it will not be overwritten by the generated one. A special case is the filter.xml which will be merged with inline filters if present.
The repository-init feature of sling-start can define initial content that will be available in the repository before the first package is installed. Packages that depend on those nodes have no way to reference any dependency package that provides these nodes. A "real" package that would creates those nodes cannot be installed in the repository, because it would void the repository init structure. On the other hand would filevault complain, if the package was listed as dependency but not installed in the repository. So therefore this repository-structure packages serve as indicator packages that helps satisfy the structural dependencies, but are not added as real dependencies to the package.
<jackrabbit-filter>
<options>
<
</options>
</jackrabbit-filter>