[
https://issues.apache.org/jira/browse/MINVOKER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958329#comment-17958329
]
Olivier Lamy commented on MINVOKER-115:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-invoker-plugin#370|https://github.com/apache/maven-invoker-plugin/issues/370].
> install goal doesn't install required plugins from the reactor build to the
> local repo
> --------------------------------------------------------------------------------------
>
> Key: MINVOKER-115
> URL: https://issues.apache.org/jira/browse/MINVOKER-115
> Project: Maven Invoker Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.5
> Environment: MacOS 10.6.6
> Mac Java 1.6
> Maven 3.0.2
> Reporter: Anders Hammar
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 1.8
>
> Attachments: MINVOKER-115-IT.patch
>
>
> In a multimodule build where the m-invoker-p is used to perform integration
> tests for an archetype. In the build, a maven plugin is first created. Then a
> maven archetype.
> For the archetype project, integration test is performed where a project is
> generated based on the archetype and then a build (mvn verify) is done.
> However, the build fails as it can't find the maven plugin built earlier in
> the reactor build. The maven-invoker-plugin:install goal installs all
> dependencies to the cloned local repo, but it doesn't install the plugin
> built.
> Update: The scenario above was the initial detection of the issue. It can
> also be seen in simpler scenarios where you have a plugin being created in
> one module and then the m-invoker-p used in another module with ITs using the
> created plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
