[
https://issues.apache.org/jira/browse/MINVOKER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053291#comment-16053291
]
Guillaume Boué commented on MINVOKER-222:
-----------------------------------------
Maybe one possibility would be to have a new {{fork}} yes / no parameter: if
yes, use current maven-invoker mechanism; if false, use maven-embedder. Not
forking would likely break thread-safety of the mojo and also
{{parallelThreads}} though (with tests setting their own, possibly conflicting,
system properties). But I'm not sure maven-embedder can be used in a plugin
context (I remember having class loading issues with EventSpyDispatcher when
trying that).
> make invoker plugin work with eclipse's embedded maven
> -------------------------------------------------------
>
> Key: MINVOKER-222
> URL: https://issues.apache.org/jira/browse/MINVOKER-222
> Project: Maven Invoker Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Gruust
> Priority: Minor
>
> Eclipse's embedded maven isn't run from an actual maven installation folder,
> so maven-invoker-plugin fails when trying to find the maven installation.
> Would be nice if we'd have some simple fallback to use the maven executable
> found on the system executable path.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
