You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2014/04/02 21:31:59 UTC
[jira] (MRELEASE-555) update versions does not update intermodule
dependencies
[ https://jira.codehaus.org/browse/MRELEASE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MRELEASE-555:
------------------------------------
Patch Submitted: Yes
> update versions does not update intermodule dependencies
> --------------------------------------------------------
>
> Key: MRELEASE-555
> URL: https://jira.codehaus.org/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
> 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.1.6#6162)