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...@codehaus.org> on 2014/11/25 21:32:08 UTC
[jira] (MAVEN-1660) DependencyVerifier class doesn't resolve an
snapshot artifact after attaining a first goal.
[ https://jira.codehaus.org/browse/MAVEN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MAVEN-1660.
---------------------------------
Resolution: Won't Fix
Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.
> DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
> -------------------------------------------------------------------------------------------
>
> Key: MAVEN-1660
> URL: https://jira.codehaus.org/browse/MAVEN-1660
> Project: Maven 1
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1-beta-1
> Reporter: Pascal Larin
> Priority: Minor
>
> Since revision 179556 of src/java/org/apache/maven/verifier/DependencyVerifier.java, the satisfyDependencies() method check if an artifact has already been resolved. It changes the behavior from version 1.0.
> For example, if you call maven with goals multiproject:clean and multiproject:deploy with artifact versions set to snaphot, maven doesn't resolve the dependencies for the multiproject:deploy because it has been already done for the multiproject:clean.
> I know that a multiproject:clean should not resolve the project dependencies but it can probably cause problems in other cases.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)