You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2015/10/28 16:46:27 UTC

[jira] [Commented] (SLING-5149) Support OSGi subsystems in slingstart-maven-plugin

    [ https://issues.apache.org/jira/browse/SLING-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978621#comment-14978621 ] 

David Bosschaert commented on SLING-5149:
-----------------------------------------

In order to support runmodes with subsystems, the slingstart-maven-plugin cannot simply create .esa files based on the provisioning model, as the selection of deployed bundles at runtime depends on the run mode. Therefore an intermediary file format is needed that contains everything needed to generate an effective subsystem at runtime based on the active run mode(s).

SLING-5210 is about the runtime side of this work.

> Support OSGi subsystems in slingstart-maven-plugin
> --------------------------------------------------
>
>                 Key: SLING-5149
>                 URL: https://issues.apache.org/jira/browse/SLING-5149
>             Project: Sling
>          Issue Type: New Feature
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Slingstart Maven Plugin 1.3.6
>            Reporter: David Bosschaert
>
> Enhance the slingstart-maven-plugin to support OSGi subsystems as modeled via SLING-5148. The maven plugin should generate an .esa file from the artifacts defined as an OSGi subsystem in the provisioning model. The resulting .esa files should be embedded in the generated archive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)