[SLING-6541] slingstart-maven-plugin: Make enriching the Maven classpath optional

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Slingstart Maven Plugin 1.7.0
• Fix Version/s: Slingstart Maven Plugin 1.7.2
• Component/s: Tooling
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 21/Feb/17 12:24
• Updated: 28/Feb/17 07:22
• Resolved: 22/Feb/17 09:11

Description

Currently the o.a.s.maven.slingstart.DependencyLifecycleParticipant takes care of enriching the Maven classpath for all projects referencing this Maven plugin. Although in most of the cases this may be desired, this is not necessarily the case.
E.g. when I have a bundle module which contains some ITs leveraging sling-mocks and others leveraging e.g. a teleporter test, the merged classpath often conflicts with sling-mocks. When using a model leveraging a slingstart project like the sling launchpad the merged classpath is huge and may negatively affect also other ITs (which are not executed remotely).

I therefore propose to make the extension of the classpath optional.

Initially this was only done for slingstart and slingfeature but changed to all projects referencing this plugin in SLING-6068.

Issue Links

• is related to: SLING-6540 Support m2e in slingstart-maven-plugin
• relates to: SLING-6068 slingstart-maven-plugin: Allow to start a quickstart JAR based on a provisioning model even for non "slingstart" packagings