You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2016/06/02 20:40:59 UTC

[jira] [Closed] (MNG-5366) [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4

     [ https://issues.apache.org/jira/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNG-5366.
-------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Issues to be reviewed for 4.x)
                   3.2.5

Fixed in Aether 0.9.0.M3 and updated in Maven with 2909b5a329fd946796428a8e7f46034bc3bcbd2f by Igor Fedorenko.

> [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
> ------------------------------------------------------------------------------
>
>                 Key: MNG-5366
>                 URL: https://issues.apache.org/jira/browse/MNG-5366
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 3.0.4, 3.0.5, 3.1.0, 3.1.1, 3.2.1, 3.2.2
>            Reporter: Paul Gier
>             Fix For: 3.2.5
>
>
> Using Maven 3.0.4, artifacts can only be resolved a single time during the build lifecycle using the Maven 2.x dependency resolution API.  Using resolver.resolveAlways() should force re-resolution of the artifact, however if the artifact was already resolved once during the build, then it will not be re-resolved even when calling resolveAlways().
> This works as expected in Maven 3.0.0-3.0.3, and the artifact is re-resolved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)