[
https://jira.codehaus.org/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298480#comment-298480
]
Mark Struberg commented on MRELEASE-426:
----------------------------------------
Well, I only used CVS from mid 90s to early 2004 or so, but I think there was a
way to checkout a branch. It was not very handy but still it used to work. Can
you please shed more light on why it is not possible to just create a branch in
CVS. I bet it would be easier to switch to SVN or GIT nowadays. Given that CVS
has horrible security leaks and is practically unmaintained since 5 years,
isn't?
> 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
