[
http://jira.codehaus.org/browse/MRELEASE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150004#action_150004
]
Kuno Baeriswyl commented on MRELEASE-380:
-----------------------------------------
Hi all,
I've investigated a bit time in this feature. I've tried to copy and modify the
branch goal in order to get my needed functionality. Unfortunately, I didn't
succeed.
I've configured following phases:
<phase>create-backup-poms</phase>
<phase>check-poms</phase>
<phase>scm-check-modifications</phase>
<phase>map-development-versions</phase>
<phase>rewrite-poms-for-development</phase>
However, they're not working well together in this configuration.
Is anybody else investigating in this thing or does anybody have any hints how
to do it?
Thanks
Kuno
> Change artifact version for whole multiproject
> ----------------------------------------------
>
> Key: MRELEASE-380
> URL: http://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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
