Maven Release Plugin
  1. Maven Release Plugin
  2. MRELEASE-341

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

          Activity

          Hide
          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
          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
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: