[jira] [Comment Edited] (SLING-6068) slingstart-maven-plugin: Allow to start a quickstart JAR based on src/main/provisioning even for non "slingstart" packagings

["Konrad Windszus (JIRA)" <ji...@apache.org>]

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

Konrad Windszus edited comment on SLING-6068 at 9/23/16 11:28 AM:
------------------------------------------------------------------

Probably the easiest way to accomplish that is leveraging a forked lifecycle with a dedicated mojo (derived from {{StartMojo}}): http://books.sonatype.com/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html. That custom lifecycle could invoke the two necessary goals {{PreparePackageMojo}} and {{PackageMojo}} before actually starting the server with the generated artifact from the forked lifecycle.
[~cziegeler] WDYT?


was (Author: kwin):
Probably the easiest way to accomplish that is leveraging a forked lifecycle with a dedicated mojo (derived from {{StartMojo}}): http://books.sonatype.com/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html. That custom lifecycle could invoke the two necessary goals {{PreparePackageMojo}} and {{PackageMojo}} before actually starting the server with the generated artifact from the forked lifecycle.

> slingstart-maven-plugin: Allow to start a quickstart JAR based on src/main/provisioning even for non "slingstart" packagings
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-6068
>                 URL: https://issues.apache.org/jira/browse/SLING-6068
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Slingstart Maven Plugin 1.4.4
>            Reporter: Konrad Windszus
>
> Currently the {{slingstart-maven-plugin}} can only start a server based on textual model definitions in case the maven module is of packaging "slingstart" (https://sling.apache.org/documentation/development/slingstart.html#starting-a-server). 
> For ITs it is often beneficial to have them in the same module as the tested classes itself (which in most cases have packaging {{bundle}}). Therefore it would be nice, if even for other packaging values all model definitions below {{src/main/provisioning}} would be considered during the goal {{start}} (which must first build the quickstart.jar out of the models and then start it).
> Compare also with the readme in https://github.com/apache/sling/blob/trunk/testing/samples/bundle-with-it/pom.xml#L196. This would be especially helpful for ITs leveraging the {{TeleporterRule}}



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