[
https://jira.codehaus.org/browse/MRELEASE-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365850#comment-365850
]
Robert Scholte commented on MRELEASE-880:
-----------------------------------------
Maven itself has 1.7M LOCs, though much less modules. But that shouldn't
matter. You might want to find out why Nexus gave the 400? Not sure if it could
be a checksum failure.
We've introduced
[deploy#deployAtEnd|http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#deployAtEnd],
which should work for common projects (let's say 80-90%), but if your project
uses extensions or other advanced Maven features, this might not work due to
current architecture of Maven. Just give it a try on the SNAPSHOTs first.
You should try to run {{mvn deploy -Papache-release}} on the SNAPSHOT sources
and see if you can reproduce it. If so, try to determine the problematic
module. If not, then it might be related to memory or so due to the overhead of
the maven-release-plugin while reinvoking Maven.
> Cannot restart from a failure
> -----------------------------
>
> Key: MRELEASE-880
> URL: https://jira.codehaus.org/browse/MRELEASE-880
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: perform
> Affects Versions: 2.5
> Reporter: Emmanuel Lécharny
> Priority: Blocker
>
> 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 :
> {noformat}
> 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.
> {noformat}
> (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.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
