[
https://jira.codehaus.org/browse/MRELEASE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=326669#comment-326669
]
Wim Deblauwe commented on MRELEASE-380:
---------------------------------------
I think the versions plugin does exactly what you want:
http://mojo.codehaus.org/versions-maven-plugin/
> Change artifact version for whole multiproject
> ----------------------------------------------
>
> Key: MRELEASE-380
> URL: https://jira.codehaus.org/browse/MRELEASE-380
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Kuno Baeriswyl
>
> In our setup one release unit defines a multiproject with a parent pom and
> several projects.
> In most cases, the release plugin supports our release process very well. The
> release plugin asks interactively for the next development version. The same
> using the branch goal, I could change the version on the trunk to any
> version. But in some cases, we just want to change the version of this
> release unit. Changing the version manually is very time-consuming and error
> prone task.
> Therefore, I'd like to suggest goal with a functionality that is essentially
> the same as for release:branch with just no SCM operations.
> Thanks
--
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
