You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mirko Friedenhagen (JIRA)" <ji...@apache.org> on 2018/10/30 11:39:00 UTC
[jira] [Comment Edited] (MDEPLOY-244) maven deploy plugin 3.0.0-M1
breaks deploys when alt*DeploymentRepository properties are used
[ https://issues.apache.org/jira/browse/MDEPLOY-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16668478#comment-16668478 ]
Mirko Friedenhagen edited comment on MDEPLOY-244 at 10/30/18 11:38 AM:
-----------------------------------------------------------------------
Seems to be the same error as in MDEPLOY-246. This is not only a problem for RPM but for standard java artifacts as well. We set {{altReleaseDeploymentRepository}} and {{altSnapshotDeploymentRepository}} globally in our settings.xml file.
The current regex at [https://gitbox.apache.org/repos/asf?p=maven-deploy-plugin.git;a=blob;f=src/main/java/org/apache/maven/plugins/deploy/DeployMojo.java;hb=72c179744b86120716e166ba59e2754b02fc1c4d#l56] is not eager, so for
central::default::https://example.com/maven2 is uses https://example.com/maven2 and central::default as id of the server (which could be used kind as workaround if you define both central and central::default entries in your settings.xml with identical user/password :-) )
was (Author: mfriedenhagen):
Seems to be the same error as in MDEPLOY-246. This is not only a problem for RPM but for standard java artifacts as well. We set {{altReleaseDeploymentRepository}} and {{altSnapshotDeploymentRepository}} globally in our settings.xml file.
> maven deploy plugin 3.0.0-M1 breaks deploys when alt*DeploymentRepository properties are used
> ---------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-244
> URL: https://issues.apache.org/jira/browse/MDEPLOY-244
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
> Affects Versions: 3.0.0-M1
> Reporter: William So
> Assignee: Karl Heinz Marbaise
> Priority: Critical
> Attachments: project-pom.xml, root-pom.xml, test-maven-deploy.zip
>
>
> After upgrading to maven deploy plugin to 3.0.0-M1, our Maven Builds that uploads an RPM artifact broke. All other artifacts, like zips, pom, jar, etc.. was able to upload without problems. But as soon as the build tried to upload an RPM the upload threw an 401 Error:
>
> [Continue Pipeline] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:3.0.0-M1:deploy (default-deploy) on project company-fancyname-atg-apptype-ibm-qa4: ArtifactDeployerException: Failed to deploy artifacts: Could not transfer artifact com.sephops.fancyname:company-fancyname-atg-apptype-ibm-qa4:rpm:ProjectName-20181001.061415-35 from/to company-snapshot-yum::default (http://artifactory.com/artifactory/company-snapshot-yum-local): Failed to transfer file: http://artifactory.com/artifactory/company-snapshot-yum-local/com/sephops/fancyname/company-fancyname-atg-apptype-ibm-qa4/ProjectName-SNAPSHOT/company-fancyname-atg-apptype-ibm-qa4-ProjectName-20181001.061415-35.rpm. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)