You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2007/03/11 20:51:34 UTC
[jira] Updated: (MAVEN-1660) DependencyVerifier class doesn't
resolve an snapshot artifact after attaining a first goal.
[ http://jira.codehaus.org/browse/MAVEN-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl updated MAVEN-1660:
---------------------------------
Fix Version/s: (was: 1.1-rc1)
> DependencyVerifier class doesn't resolve an snapshot artifact after attaining a first goal.
> -------------------------------------------------------------------------------------------
>
> Key: MAVEN-1660
> URL: http://jira.codehaus.org/browse/MAVEN-1660
> Project: Maven 1.x
> 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 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