[
https://issues.apache.org/jira/browse/MDEPLOY-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965620#comment-17965620
]
Olivier Lamy commented on MDEPLOY-114:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#152|https://github.com/apache/maven-deploy-plugin/issues/152].
> Add an option to not fail when remote file already exists and redeploy is
> forbidden
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-114
> URL: https://issues.apache.org/jira/browse/MDEPLOY-114
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Wish
> Components: deploy:deploy
> Affects Versions: 2.4
> Reporter: Julien HENRY
> Assignee: Robert Scholte
> Priority: Major
> Labels: contributers-welcome
>
> In my organisation we are using a MRM (Nexus) with redeployment of release
> that is forbidden.
> Sometimes the release:perform may fail in the middle of a multi-module
> release. It means some modules were deployed but other are not.
> Currently it is not possible to restart the release as it will fail on first
> deployment (usually the parent pom of the multimodule) because the pom was
> already deployed during the first attempt.
> I would like to add an option to the deploy plugin that may deal with this
> case. Perhaps an option like -Dredeploy=false that may either :
> 1) check if the remote file already exists before trying to upload
> 2) try to upload everytime but not fail the build
> The problem with the second proposal is the error returned by Nexus is
> authorization error so we may not be able to distinguish real authorization
> error on a new file and redeploy attempt.
> Caused by: org.apache.maven.wagon.authorization.AuthorizationException:
> Access denied to: http://nexus.mycompany.com/
> content/repositories/myrepo/com/mycustomer/project/parent/3.2.0/parent-3.2.0.pom
> at
> org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:360)
> Other options may be more complicated like implementing an atomic deploy
> process on multimodule (may need a big change of the deploy protocol).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
