[
https://issues.apache.org/jira/browse/SLING-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876020#comment-15876020
]
Konrad Windszus commented on SLING-6541:
----------------------------------------
Yes, this works.
> slingstart-maven-plugin: Make enriching the Maven classpath optional
> --------------------------------------------------------------------
>
> Key: SLING-6541
> URL: https://issues.apache.org/jira/browse/SLING-6541
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: Slingstart Maven Plugin 1.7.0
> Reporter: Konrad Windszus
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
