[ http://jira.codehaus.org/browse/MAVEN-1660?page=comments#action_44931 ]
Pascal Larin commented on MAVEN-1660: ------------------------------------- Hum... In our case, it won't work. We have around 50 subprojects, each project is set to snapshot. It happens sometime that a subproject needs changes from a component previously build in the same multiproject:deploy. I've made patch to always resolve a dependency if it is a snapshot version. One thing is sure, Maven 1.1 behave differently than 1.0 with this revision (179556). Pascal > 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 > Type: Bug > Components: core > Versions: 1.1-beta-1 > Reporter: Pascal Larin > Priority: Minor > Fix For: 1.1-beta-2 > > > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
