[
https://issues.apache.org/jira/browse/SLING-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875875#comment-15875875
]
Konrad Windszus edited comment on SLING-6540 at 2/21/17 12:09 PM:
------------------------------------------------------------------
The remaining tricky part is the {{DependencyLifecycleParticipant}}. By
default it is not executed from m2e
(https://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00841.html) leading to
different classpaths in Maven CLI vs. M2E based builds.
To support m2e properly the according functionality should also be triggered
from a project configurator. [~cziegeler] WDYT?
was (Author: kwin):
The only question is if the {{DependencyLifecycleParticipant}} can be executed
from m2e as well. By default this is not the case
(https://dev.eclipse.org/mhonarc/lists/m2e-dev/msg00841.html) leading to
different classpaths in Maven CLI vs. M2E based builds.
> Support m2e in slingstart-maven-plugin
> --------------------------------------
>
> Key: SLING-6540
> URL: https://issues.apache.org/jira/browse/SLING-6540
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: Slingstart Maven Plugin 1.7.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Minor
> Fix For: Slingstart Maven Plugin 1.7,2
>
>
> Currently all goals of the {{slingstart-maven-plugin}} do not support m2e
> (https://www.eclipse.org/m2e/documentation/m2e-making-maven-plugins-compat.html).
> All goals should be ignored in the incremental build for now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
