[
https://jira.codehaus.org/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298481#comment-298481
]
Jörgen Persson commented on MRELEASE-426:
-----------------------------------------
Ok. From my point of view, it's not CVS we're using in my company, but SVN.
I would like to have the possibility to specify -DscmVersion=<some revision>
when making a release and it is due to the following.
We have official releases and we have alpha or beta releases. When making an
alpha or beta release, we are not allowed to make any release branches as this
should not be maintained in a traditional way with bug fix releases and so as
we do in official releases.
Sometimes when there is a need for such a alpha or beta release, and due to a
time consuming release procedure (an rough estimate is half a day, due to a lot
of test cases, packaging, assemblying, ...), what I would like, is for my
colleagues, to grab a snapshot version from our Jenkins server and do QA / test
on it. If the QA / tests were successful there are normally a lot of commits
made on our trunk.
This is why I would like to release and tag trunk as how it looked at <some
revision> and not HEAD.
> There is no way to specify a branch/tag/revision when performing a release
> --------------------------------------------------------------------------
>
> Key: MRELEASE-426
> URL: https://jira.codehaus.org/browse/MRELEASE-426
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.0-beta-8
> Environment: Maven2, CVSNT
> Reporter: Eric
>
> When using the release-plugin with CVS, there does not seem to be any way to
> specify a version & versionType to base the release on.
> The scm plugin allows to specify scmVersion, scmVersionType to pass this
> information to the plugin, but when calling the release:perform goal, there
> is no way to send this information to the scm plugin to checkout the files
> from the appropriate branch/tag.
> Accordingly, it seems that with CVS, the only way to build a release is from
> the latest sources in the HEAD; not extremely practical.
--
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
