[jira] Closed: (MINVOKER-70) invoker:install does not properly handle versioned dependencies

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MINVOKER-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MINVOKER-70.
-------------------------------------

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: 1.4

Fixed in [r706426|http://svn.apache.org/viewvc?view=rev&revision=706426], snapshot deployed.

Jared, thanks for the test! The problem was that the plugin installed snapshot artifacts with the timestamped version instead of just "*-SNAPSHOT" as required for local repos.

> invoker:install does not properly handle versioned dependencies
> ---------------------------------------------------------------
>
>                 Key: MINVOKER-70
>                 URL: http://jira.codehaus.org/browse/MINVOKER-70
>             Project: Maven 2.x Invoker Plugin
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Jared Roberts
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>             Fix For: 1.4
>
>         Attachments: MINVOKER-70-Example.zip
>
>
> The fix for MINVOKER-64 introduced a regression. Previously, only the artifact under test was installed to the IT local repository. The other dependencies were then resolved from remote repositories. In 1.3, the other dependencies are pulled from the actual local repository. It appears that the resolution of uniquely versioned dependencies is different in the two flows because the 1.2.1 flow downloaded both the uniquely versioned jar and the non-unique jar but the 1.3 flow only installs the uniquely versioned jar. My build now fails because it cannot find the non-uniquely versioned jar to run my integration tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira