-
Notifications
You must be signed in to change notification settings - Fork 73
Closed
Labels
bugSomething isn't workingSomething isn't workingpriority:minorMinor loss of function, or other problem where easy workaround is presentMinor loss of function, or other problem where easy workaround is present
Description
Ryan Parrish opened MDEPLOY-182 and commented
Summary
If there is a pluginRepository defined in the POM, and the installAtEnd configuration is true, the actual local repo installation at the end of the build is skipped.
Expectation is that the local repo installation at the end of the build would work regardless of pluginRepository configuration.
Steps
- In the trunk/2.6-SNAPSHOT project, run
mvn installthe install-at-end-pass integration test. The install happens successfully at the end of the build (see console output attached). - Add a pluginRepository definition to install-at-end-pass/pom.xml, such as
<pluginRepositories>
<pluginRepository>
<id>central</id>
<name>Maven Plugin Repository</name>
<url>http://repo1.maven.org/maven2</url>
<layout>default</layout>
</pluginRepository>
</pluginRepositories>
- Re-run the
mvn install. Observe that the install to local repo is not performed (see attached install-at-end-pass_withpluginrepo.txt console output).
Workaround
Define the pluginRepositories in settings.xml, not in the current POM lineage. The installAtEnd works as expected in this case.
Affects: 2.5, 2.6
Issue Links:
- MDEPLOY-179 deployAtEnd bypassed in case of pluginRepository definition
("duplicates")
Remote Links:
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingpriority:minorMinor loss of function, or other problem where easy workaround is presentMinor loss of function, or other problem where easy workaround is present