[SLING-6068] slingstart-maven-plugin: Allow to start a quickstart JAR based on a provisioning model even for non "slingstart" packagings

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Slingstart Maven Plugin 1.4.4
• Fix Version/s: Slingstart Maven Plugin 1.5.0
• Component/s: Maven Plugins and Archetypes
• Assignee: Carsten Ziegeler
• Reporter: Konrad Windszus
• Created: 23/Sep/16 11:02
• Updated: 21/Feb/17 12:24
• Resolved: 08/Nov/16 08:51

Description

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

Issue Links

• is related to: SLING-6107 slingstart-maven-plugin: Implement caching for goals "package" and "prepare-package"
• is related to: SLING-6541 slingstart-maven-plugin: Make enriching the Maven classpath optional
• links to: GitHub Pull Request #176