deployAtEnd bypassed in case of pluginRepository definition

Summary

If there is a pluginRepository defined in the POM, and the deployAtEnd configuration is true, the actual repo deployment at the end of the build is skipped.

Expectation is that the repo deployment at the end of the build would work regardless of pluginRepository configuration.

Steps

1. In the trunk/2.9-SNAPSHOT project, run mvn deploy the deploy-at-end-pass integration test. The deploy happens successfully at the end of the build.
2. Add a pluginRepository definition to deploy-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 deploy. Observe that the deploy to repo is not performed.

Workaround

Define the pluginRepositories in settings.xml, not in the current POM lineage. The deployAtEnd works as expected in this case.