You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Igor Fedorenko (JIRA)" <ji...@codehaus.org> on 2014/08/28 13:10:10 UTC
[jira] (MNG-5366) [Regression] resolveAlways does not force
dependency resolution in Maven 3.0.4
[ https://jira.codehaus.org/browse/MNG-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351953#comment-351953 ]
Igor Fedorenko commented on MNG-5366:
-------------------------------------
This maybe fixed by the new aether I just integrated in maven, but hard to tell for sure without example project or unit test to demonstrate the original problem.
> [Regression] resolveAlways does not force dependency resolution in Maven 3.0.4
> ------------------------------------------------------------------------------
>
> Key: MNG-5366
> URL: https://jira.codehaus.org/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: Issues to be reviewed for 4.x
>
>
> 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.1.6#6162)