Maven 2.x Release Plugin

support release process that use a staging repository

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-8
  • Fix Version/s: 2.0-beta-8
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Many release process (ex: geronimo) require the release candidate to be exposed in a staging repository for testing, then vote from the communiity, and finally copy the artifact in the public repository / web site. This requires to run the release:perform with the final version (not a "-rc*" one).

When the vote fails, the release manager has to rollback the project to the previous SNAPSHOT version. As release:perform removes all the release-related files (including pom backups) the release:rollback goal cannot be used for this.

Geronimo solution is to copy the trunk as a "savepoint" before staging a release. A far better option would be to have a dedicated goal for this "release:stage" :

  • same features as release:perform
  • don't remove release.properties and backups
  • requires a stagingRepository parameter, to be passed as -DaltRepoLocation to the deploy plugin
  • detect the site:deploy goal and replace it with site:stage-deploy

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. MRELEASE-340 Don't store the scm password in plaintext in release.properties

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
nicolas de loof added a comment -

new release:stage Mojo with documentation

Show
nicolas de loof added a comment - new release:stage Mojo with documentation
Hide
Permalink
Wendy Smoak added a comment -

I'm linking this to MRELEASE-340 because leaving the release.properties file around is a potential security risk. That file has the scm credentials in plain text. We should at least mention this in the docs.

Does this need to be a separate goal or would another parameter on release:perform work, since it already understands the alternate deployment repository?

Show
Wendy Smoak added a comment - I'm linking this to MRELEASE-340 because leaving the release.properties file around is a potential security risk. That file has the scm credentials in plain text. We should at least mention this in the docs. Does this need to be a separate goal or would another parameter on release:perform work, since it already understands the alternate deployment repository?

People

  • Assignee:
    nicolas de loof
    Reporter:
    nicolas de loof
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: