jira-importer opened a new issue, #542: URL: https://github.com/apache/maven-invoker-plugin/issues/542
**[Konrad Windszus](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kwin)** opened **[MINVOKER-314](https://issues.apache.org/jira/browse/MINVOKER-314?redirect=false)** and commented Due to the logic in https://github.com/apache/maven-invoker-plugin/blob/166b7295632bce336837a2ab9b7231b0003a7f12/src/main/java/org/apache/maven/plugins/invoker/InstallMojo.java#L422 which only installs those dependencies which are part of the reactor the outcome of the same IT might differ depending on whether the module is build alone or in the reactor (even if the reactor has been installed before to the regular local repository with "mvn install"). To make the IT and install goal always behave the same just all dependencies should be installed to the local repo (no matter if part of the reactor or not). --- **Issue Links:** - [MINVOKER-313](https://issues.apache.org/jira/browse/MINVOKER-313) Get rid of maven-artifact-transfer (_**"is blocked by"**_) - [MINVOKER-317](https://issues.apache.org/jira/browse/MINVOKER-317) invoker:install installs different sets of dependencies, depending on the reactor build -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
