[
https://issues.apache.org/jira/browse/SLING-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516681#comment-15516681
]
Carsten Ziegeler commented on SLING-6068:
-----------------------------------------
I think the only piece that is missing is running of the
DependencyLifecycleParticipant - that checks for the package type. That's
basically to improve performance on large reactor builds. We could relax this
and check for projects having the slingstart maven plugin configured. I think
just changing that should solve the problem,
> 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)
