Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-880

Cannot restart from a failure

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 2.5
    • None
    • perform
    • None

    Description

      It's currently quite impossible to cut a release on a big Apache project if the remote server has hickups.

      I tried to release Apache Directory Server this morning, and for some unknown reasons, I get various and random failures like :

      Failed to execute goal
      org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy
      (default-deploy) on project apacheds-core-api: Failed to deploy
      artifacts: Could not transfer artifact
      org.apache.directory.server:apacheds-core-api:jar:tests:2.0.0-M17
      from/to apache.releases.https
      (https://repository.apache.org/service/local/staging/deploy/maven2):
      Failed to transfer file:
      https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/directory/server/apacheds-core-api/2.0.0-M17/apacheds-core-api-2.0.0-M17-tests.jar.
      Return code is: 400, ReasonPhrase: Bad Request.
      

      (note that if I restart the release:perform, the error I will get will be different).

      There is no way I can restart the perform from another point (like the failing module) but the very beginning.

      At the very end, I did a mvn deploy -Papache-release from target/checkout as a workaround...

      The real pb is that the release plugin should not simply bail when it gets some error attempting to reach a remote server. Asking the user about doing a retry should be the way to go.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              elecharny Emmanuel L├ęcharny
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: