Apache Sling Content Package to Feature Model Plugin
This module is part of the Apache Sling project.
Maven Plugin for Content Package to Feature Model Conversion:
Introduction
This plugin is intended for a content package to also provide a Feature Model and its converted package / bundle. This plugin will only work on Content Package ZIP files artifacts.
This plugin is a wrapper for the Sling Feature Content Package Converter org.apache.sling.feature.cpconverter over a content package the POM defines.
The idea is to convert a Content Package at built time into a Feature Module so that it can be used both a regular Content Package in a traditional Sling Instance (Lauchpad) or in a Sling Instance in a Feature Model. The plugin will do the conversion and so a Content Package cna be used in a Feature Model w/o any changes in the Content Package.
Supported goals
This plugin has only one goal called convert-cp which takes a few parameters:
- strictValidation: if set to true this will force the plugin to do a strict conversion. Checkout the Content Package 2 Feature Model Converter tool. Default: false
- mergeConfigurations: if set to true if will merge configurations with the same PID. Not sure if that makes sense in this plugin. Default: false
- bundleStartOrder: The bundle start order of the generated Feature Model. Default 20
- artifactIdOverride: An FM Artifact Id that overrides the one that is set by default. Atttention: to avoid the variable substitution for ${} please add a zero-width whitespace () in between.
- featureModelsOutputDirectory: Output folder of the Feature Model. Default target/cp-conversion
- convertedContentPackageOutputDirectory: Output folder folder of the converted Content Package. Default target
- installConvertedContentPackage: Install the Converted Content Package into the local Maven Repository so that it can be used by the Feature Model without a manual copy. Default: true
- systemProperties: List of strings that represents System Properties like the Java -D option
In order for the plugin to work the Content Package must be already created so this plugin must be started in a lifecycle phase after package.