Apache Sling Feature Converter Maven Plugin

Clone this repo:

Branches

  1. bba2613 Added the installation of the FM created by the converter if this plugin is used on a Content Package module by Andreas Schaefer · 3 weeks ago master
  2. 69b4b9b Updated Git Ignores by Andreas Schaefer · 3 months ago
  3. e77c109 Updated Sling Feature dependencies to the latest release and extracted all version numbers into properties by Andreas Schaefer · 3 months ago
  4. 638bd71 Cleaning up the POM dependencies and update the docu by Andreas Schaefer · 4 months ago
  5. fc8aec4 Adjusted the Converted to the addition of the Prefix by Andreas Schaefer · 4 months ago

Build Status Test Status Maven Central JavaDocs License

Apache Sling Feature Converter Maven Plugin

This module is part of the Apache Sling project.

This plugin provides the means to convert both Content Packages as well as Provisioning Models into Feature Models through a POM file.

Introduction

This plugin is intended to convert:

  • Content Packages
  • Provisioning Models into Feature Models so that it can be used by the Sling Feature Maven Plugin to assemble and run.

This plugin is a wrapper for the Sling Feature Content Package Converter sling-org-apache-sling-feature-cpconverter and the Sling Feature Model Converter sling-org-apache-sling-feature-modelconveter to convert source files into Feature Models inside a POM.

This plugin is normally used to convert Sling into its Feature Model version and to convert Content Packages into Feature Models so that they can be handled by the Sling Feature Maven Plugin and eventually launched.

Supported goals

These Goals are support in this plugin:

  • convert-cp: Converts Content Packages into Feature Model files and its converted ZIP files
  • convert-pom: Converts Provisioning Models into Feature Models

See the Site documentation for further info.

Content Package Handling

The installation of Converted Content Packages has be difficult at times.

These are the things fo far that should help making this easier:

  1. Make sure that you use the latest code base
  2. Make sure that during the launch:
    1. Sling Feature Extension Content is added first as Plugin Dependency (any extension should be added before the Launcher)
    2. Add Sling Feature Launcher as Plugin Dependency afterwards
    3. Make sure that the JCR Package Init is added as Feature (see Site Documentation Usage)
  3. After Feature is up and running log into OSGi Console and check OSGi Installer to make sure there are no Untransformed Resources
  4. During development make sure that the Launcher folder is deleted periodically to avoid side effects from previous launches