Maven 2.x Release Plugin

There is no way to specify a branch/tag/revision when performing a release

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0-beta-8
  • Fix Version/s: None
  • Component/s: perform
  • Labels:
    None
  • Environment:
    Maven2, CVSNT
  • Number of attachments :
    0

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Eric added a comment -

Typo - I meant ".. The scm plugin allows to specify scmVersion, scmVersionType to pass this information to cvs, but ..."

Show
Eric added a comment - Typo - I meant ".. The scm plugin allows to specify scmVersion, scmVersionType to pass this information to cvs, but ..."
Hide
Permalink
Jörgen Persson added a comment -

It's an old post / issue, but I agree with the issue creator.
It would be very very convenient to be able to make a release from an earlier revision than HEAD

Show
Jörgen Persson added a comment - It's an old post / issue, but I agree with the issue creator. It would be very very convenient to be able to make a release from an earlier revision than HEAD
Hide
Permalink
Mark Struberg added a comment -

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?

Show
Mark Struberg added a comment - 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?
Hide
Permalink
Jörgen Persson added a comment - - edited

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 in the mean time.
This is why I would like to release and tag trunk as how it looked at <some revision> and not HEAD.

Show
Jörgen Persson added a comment - - edited 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 in the mean time. This is why I would like to release and tag trunk as how it looked at <some revision> and not HEAD.

People

  • Assignee:
    Unassigned
    Reporter:
    Eric
Vote (2)
Watch (4)

Dates

  • Created:
    Updated: