[
https://issues.apache.org/jira/browse/MRELEASE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733064#comment-14733064
]
Kogler Hannes (HKO 4530) commented on MRELEASE-426:
---------------------------------------------------
Dear Sir or Madam,
Thank you for your message. I am out of the office at the moment and will be
back on Thursday, 24th. September 2015.
I will reply to your e-mail as soon as possible when I return.
Please note that I will have limited access to my e-mail and your message will
not be forwarded automatically.
For urgent issues may I refer you to my colleagues Michael Weichselbaumer (MWE)
and Ronald Angerer (RAN).
Best regards
Hannes Kogler
Software Engineer
Registered Office | NTS New Technology Systems GmbH
Doernbacherstraße 126 | 4073 Wilhering | Austria
FN155693k | ATU42651803 | Court of Jurisdiction Linz
> There is no way to specify a branch/tag/revision when performing a release
> --------------------------------------------------------------------------
>
> Key: MRELEASE-426
> URL: https://issues.apache.org/jira/browse/MRELEASE-426
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: perform
> Affects Versions: 2.0-beta-8
> Environment: Maven2, CVSNT
> Reporter: Eric B
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
