[
https://issues.apache.org/jira/browse/MRELEASE-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-380.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Change artifact version for whole multiproject
> ----------------------------------------------
>
> Key: MRELEASE-380
> URL: https://issues.apache.org/jira/browse/MRELEASE-380
> Project: Maven Release Plugin
> Issue Type: New Feature
> Components: scm
> Affects Versions: 2.0-beta-7
> Reporter: Kuno Baeriswyl
> Priority: Major
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
