[MDEPLOY-182] deployAtEnd bypassed in case of pluginRepository definition

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.5, 2.6

Environment

Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 05:51:28-0800)
Java version: 1.7.0_45, vendor: Oracle Corporation
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"

• Assignee: Robert Scholte
• Reporter: Ryan Parrish
• Created: 21/Apr/14 19:06
• Updated: 03/Jul/14 13:48
• Resolved: 03/Jul/14 13:48

Description

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

1. In the trunk/2.6-SNAPSHOT project, run mvn install the install-at-end-pass integration test. The install happens successfully at the end of the build (see console output attached).
2. 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>
     

3. 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.

Issue Links

• duplicates: MDEPLOY-179 deployAtEnd bypassed in case of pluginRepository definition