The Analyser can analyse features for completeness and correctness. The analyser is pluggable and can also perform other checks.
The analyser can be run from the commandline by running the following main class:
The Analyser can also be run as part of a maven build via the
The following analysers are defined:
bundle-packages: Checks bundle import/export package statements for consistency and completeness. Does not take API Regions into account. An expanded variant of this analyser is available in org-apache-sling-feature-extension-apiregions under the name
bundle-content: Gives a warning if a bundle container initial content specified with
bundle-resources: Gives a warning if a bundle contains resources specified with
compare-features: Compares the artifacts in the bundles sections or in an extension between two feature models. For more information see below.
requirements-capabilities: Checks bundle requirements/capabilities for consistency and completeness.
apis-jar: Validates that the entries related to Apis Jar are valid.
repoinit: Checks the syntax of all repoinit sections.
Additional analysers in relation to Feature Model API Regions can be found here: https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions
For further documentation see: https://github.com/apache/sling-org-apache-sling-feature/blob/master/readme.md
This analyser compares certain sections of two feature models.
This analyser requires additional configuration:
|Configuration key||Allowed values||Description|
|The types of entities being compared. Currently only artifacts can be compared.|
|Maven ID, e.g. ||The golden feature to compare the features selected for the analyser with.|
|extension name||If this configuration is absent, the feature's bundles are compared. Otherwise the extensions with the specified name are compared. These extensions must be of type |
|Whether the sections must be the same or must be different. Defaults to |
|Whether to include the artifact metadata in the comparison. Defaults to |