[ 
http://jira.codehaus.org/browse/MRELEASE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95484
 ] 

Chris Wewerka commented on MRELEASE-161:
----------------------------------------

With 2.0-beta-5 and maven 2.0.6 a related issue (two dependencies to a project, 
one to the normal artifact, one to the test-jar) results in an error:

 [INFO] ------------------------------------------------------------------------
 [ERROR] BUILD ERROR
 [INFO] ------------------------------------------------------------------------
 [INFO] Failed to resolve artifact.

 Missing:
 ----------
 1) com.o2.release-test:release-test-module-one:test-jar:tests:5.0.2


I've attached a testcase to reproduce this bug.

> If there is more than one artifact with the same artifactId in 
> dependencyManagement only the first one is updated
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-161
>                 URL: http://jira.codehaus.org/browse/MRELEASE-161
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>         Environment: Maven 2.0.4 under windows
>            Reporter: Sébastien Cesbron
>         Attachments: multipleArtifacts.patch
>
>
> I have a multi module project. When I do release:prepare, the release plugin 
> update the version tag of all my submodules in the dependencyManagement 
> section.
> For the same module I have declared two artifacts like this :
>       <dependency>
>         <groupId>com.bla</groupId>
>         <artifactId>blabla</artifactId>
>         <version>1.0-SNAPSHOT</version>
>         <type>test-jar</type>
>         <scope>test</scope>
>       </dependency>
>       <dependency>
>         <groupId>com.bla</groupId>
>         <artifactId>blabla</artifactId>
>         <version>1.0-SNAPSHOT</version>
>       </dependency>
> In this case, the release plugin only update the first dependency.
> This is due to element search in the "updateDomVersion" method of the 
> AbstractRewritePomsPhase class. I've attached a patch to solve the problem. I 
> don't know if this is the right  way to do. I change all the artifacts in the 
> same pass. I don't take car of different type/classifier

-- 
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


Reply via email to