[
https://jira.codehaus.org/browse/MRELEASE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Gibson updated MRELEASE-555:
---------------------------------
Attachment: MRELEASE-555.patch
I needed this feature, and so I added it. The property that controls
intermodule dependency updating is {{updateDependencies}}, just like the
{{prepare}} goal. However, it defaults to {{false}} rather than {{true}} to
maintain backwards compatibility.
Note that there is not a unit test for this feature, but then again there are
no unit tests for the update-versions goal at all.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
