[
https://issues.apache.org/jira/browse/SLING-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217127#comment-17217127
]
Andreas Schaefer commented on SLING-9581:
-----------------------------------------
I started to look into the two Maven Plugin.
The Kickstart Maven Plugin is tied to the Kickstart module (Sling) and does
start that Sling in the process together with the Feature Model from the Maven
project. It can keep the launched system alive after the Maven build ends.
The Feature Launcher Maven Plugin just start the given Feature Model from the
Maven project but it allows to start multiple instances (not sure what this is
intended to do).
To unify the two I could add a property that allows to run the Kickstart system
would just run with the Feature Model of the Maven project.
> Reduce implementation duplication between kickstart and feature-launcher
> maven plugin
> -------------------------------------------------------------------------------------
>
> Key: SLING-9581
> URL: https://issues.apache.org/jira/browse/SLING-9581
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.2, Feature Model Sling
> Kickstart Project 0.0.10, Feature Model Sling Maven Kickstart Plugin 0.0.10
>
>
> There is an implementation overlap between the kickstart tooling and the
> feature-launcher maven plugin. We should remove it to ensure our tooling
> behaves consistently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
