Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.0.0, 3.0.1
-
None
-
None
-
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T22:39:06+03:00)
Maven home: C:\Tools\mvn3.5.0\bin\..
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_144\jre
Default locale: en_US, platform encoding: Cp1251
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T22:39:06+03:00) Maven home: C:\Tools\mvn3.5.0\bin\.. Java version: 1.8.0_144, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.8.0_144\jre Default locale: en_US, platform encoding: Cp1251 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Description
Installing extra artifacts from local maven repository worked with maven-invoker-plugin 2.0.0, but stopped to work in 3.0.0.
Steps to reproduce:
- extract archive
- in project1 run mvn install to install it to local maven repository
- in project2 run mvn invoker:install. It fails to install project1 to a custom repository when it is specified as an extra artifact.
Attachments
Attachments
Issue Links
- relates to
-
MINVOKER-249 InstallMojo extraArtifacts are always downloaded (optionally local repo must checked first)
- Closed