jira-importer commented on issue #652: URL: https://github.com/apache/maven-invoker-plugin/issues/652#issuecomment-2957811845
**[Karl Heinz Marbaise](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=khmarbaise)** commented The problem can simply be solved by using a dependency to project-2 in your project-3. The thing is that the order of the reactor causes this problem. The maven-invoker-plugin:install will get all dependencies and all artifacts from the reactor. Excerpt from the docs: > More precisely, all artifacts of the project itself, all its locally reachable parent POMs and all its dependencies from the reactor will be installed to the local repository. The root cause here is the order of execution which is defined by the dependencies between the modules in the reactor. The reactor itself can't be influenced by a plugin....for example to add dependencies to change the order, cause the plugin will too late when the topological sorting of the reactor has already been done. So the real question is: Is install goal doing it right? After thinking about this it does not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
