[jira] (MINSTALL-104) installAtEnd bypassed in case of pluginRepository definition

["Robert Scholte (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MINSTALL-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MINSTALL-104.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Robert Scholte

This is a Maven Core issue which can't be fixed by the plugin. It seems like the instances of the maven-install-plugin end up in different ClassRealms, so the plugin can't detect when it's ready. 
This is one those edge-cases where deployAtEnd won't work, hence the reason why it's default value is still false.
We're investigating improvements on the lifecycle handling for the next major release of Maven.

> installAtEnd bypassed in case of pluginRepository definition
> ------------------------------------------------------------
>
>                 Key: MINSTALL-104
>                 URL: https://jira.codehaus.org/browse/MINSTALL-104
>             Project: Maven Install Plugin
>          Issue Type: Bug
>          Components: install:install
>    Affects Versions: 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"
>            Reporter: Ryan Parrish
>            Assignee: Robert Scholte
>            Priority: Minor
>         Attachments: install-at-end-pass_original.txt, install-at-end-pass_withpluginrepo.txt
>
>
> h2. 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.
> h2. Steps
> # In the [trunk/2.6-SNAPSHOT|http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin] 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).
> # Add a pluginRepository definition to install-at-end-pass/pom.xml, such as
>   {code}
>  <pluginRepositories>
> 	<pluginRepository>
>       <id>central</id>
>       <name>Maven Plugin Repository</name>
>       <url>http://repo1.maven.org/maven2</url>
>       <layout>default</layout>
>     </pluginRepository>
>   </pluginRepositories>
>   {code}
> #  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).
> h2. Workaround
> Define the pluginRepositories in settings.xml, not in the current POM lineage.  The installAtEnd works as expected in this case.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)