maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reimo Daum (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRELEASE-161) If there is more than one artifact with the same artifactId in dependencyManagement only the first one is updated
Date Tue, 01 Feb 2011 09:18:59 GMT

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

Reimo Daum updated MRELEASE-161:
--------------------------------

    Attachment: MRELEASE-161.patch

I attached possible solution for this bug - it does not break tests but i'm not sure if it's
a correct way to solve this issue as this loop break has been there for ages.

My solutions is not to break the loop as there are also other dependendcies with same "groupId
+ artifactId" but different type.

> 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
>          Components: prepare
>    Affects Versions: 2.0-beta-4
>         Environment: Maven 2.0.4 under windows
>            Reporter: S├ębastien Cesbron
>         Attachments: MRELEASE-161.patch, multipleArtifacts.patch, release-test.zip
>
>
> 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 :
> {code:xml}
> <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>
> {code}
> 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

       

Mime
View raw message