maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MRELEASE-555) update versions does not update intermodule dependencies
Date Mon, 06 Apr 2015 09:33:13 GMT

     [ https://issues.apache.org/jira/browse/MRELEASE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed MRELEASE-555.
-----------------------------------
    Resolution: Fixed

Fixed in [r1671270|http://svn.apache.org/r1671270]

> update versions does not update intermodule dependencies
> --------------------------------------------------------
>
>                 Key: MRELEASE-555
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-555
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: update-versions
>    Affects Versions: 2.0
>         Environment: Maven 2.2.1, JDK 6, XP SP3
>            Reporter: Michael Osipov
>            Assignee: Robert Scholte
>             Fix For: 2.5.2
>
>         Attachments: MRELEASE-555.patch
>
>
> I recently tried the update-versions goal which is really nice and worked well. I cleaned
my local repo today and reran "mvn package" on a multi-module project. It failed due tue a
depenceny error.
> My project was previously on version 2.6.1-SNAPSHOT. Module war depends on module jar
with the same version. When doing a release:prepare, the plugin  perfectly bumps this intermodule
dependency. The release:update-versions missed that dep spot. My build process failed.
> The goal should crawl for those deps too and update them if autoVersionSubmodules is
on. (Same behavior as the prepare goal)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message