You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcin Zajaczkowski (JIRA)" <ji...@codehaus.org> on 2012/06/22 13:40:21 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:comment-tabpanel&focusedCommentId=301702#comment-301702 ]
Marcin Zajaczkowski commented on MRELEASE-555:
----------------------------------------------
This works fine also with release:branch. The same could be used in update-versions.
> update versions does not update intermodule dependencies
> --------------------------------------------------------
>
> Key: MRELEASE-555
> URL: https://jira.codehaus.org/browse/MRELEASE-555
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: update-versions
> Affects Versions: 2.0
> Environment: Maven 2.2.1, JDK 6, XP SP3
> Reporter: Michael Osipov
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira