You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eric (JIRA)" <ji...@codehaus.org> on 2009/03/16 20:52:12 UTC
[jira] Commented: (MRELEASE-426) There is no way to specify a
branch/tag/revision when performing a release
[ http://jira.codehaus.org/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=169864#action_169864 ]
Eric commented on MRELEASE-426:
-------------------------------
Typo - I meant ".. The scm plugin allows to specify scmVersion, scmVersionType to pass this information to cvs, but ..."
> There is no way to specify a branch/tag/revision when performing a release
> --------------------------------------------------------------------------
>
> Key: MRELEASE-426
> URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira