Full name:
org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package
Description:
Attributes:
| Name | Type | Since | Description |
|---|---|---|---|
| <enforceRecursiveSubpackageValidation> | boolean | - | If set to true always executes all validators also for
all sub packages (recursively). Default value is: false. |
| <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. |
| <packageFile> | File | - | The package file to validate. By default will be the project's
artifact (in case a project is given) Default value is: ${project.artifact.file}. User property is: vault.packageToValidate. |
| <skipValidation> | boolean | - | (no description) Default value is: false. User property is: vault.skipValidation. |
| Name | Type | Since | Description |
|---|---|---|---|
| <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 []
<jackrabbit-dependencies>
<defaultSeverity>debug</defaultSeverity>
</jackrabbit-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.
<jackrabbit-filter>
<options>
<
</options>
</jackrabbit-filter>