You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/01/08 23:31:00 UTC

[jira] [Commented] (MRELEASE-161) If there is more than one artifact with the same artifactId in dependencyManagement only the first one is updated

    [ https://issues.apache.org/jira/browse/MRELEASE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737647#comment-16737647 ] 

Hudson commented on MRELEASE-161:
---------------------------------

Build failed in Jenkins: Maven TLP » maven-release » master #65

See https://builds.apache.org/job/maven-box/job/maven-release/job/master/65/

> If there is more than one artifact with the same artifactId in dependencyManagement only the first one is updated
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-161
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-161
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-4
>         Environment: Maven 2.0.4 under windows
>            Reporter: Sébastien Cesbron
>            Assignee: Robert Scholte
>            Priority: Major
>              Labels: up-for-grabs
>         Attachments: MRELEASE-161.patch, multipleArtifacts.patch, release-test.zip
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)