[
https://issues.apache.org/jira/browse/SLING-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15522573#comment-15522573
]
Konrad Windszus commented on SLING-6068:
----------------------------------------
Actually for the case I have in mind, the dependencies are not important.
Whenever you want to test a bundle with an integration test, relying on a
provisioned Sling instance based only on a textual provisioning model would be
very handy, from where it is build and started prior to IT execution.
Therefore I would propose the following changes:
# Within the {{DependencyLifecycleParticipant}} not only pick up models from
{{src/main/provisioning}} but also from {{test/main/provisioning}}. In the
latter case only add the generated dependencies to the according project with
scope {{test}}.
# Let the {{DependencyLifecycleParticipant}} deal with all modules having such
a provisioning model (independent of their packaging)
# Come up with an aggregate mojo which sequentially triggers
{{prepare-package}}, {{package}} and {{start}}. This is just to make it easier
to leverage such a setup without being forced to explicitly configure three
different goals.
# In the best case do some kind of caching so that packaging is only done if
the latest quickstart artifact does no longer represent the provisioning model.
WDYT?
> slingstart-maven-plugin: Allow to start a quickstart JAR based on a
> provisioning model 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)
