[jira] [Created] (MNG-6785) Fail to deploy on Sonatype OSS since maven 3.5.4

["Stephane Landelle (Jira)" <ji...@apache.org>]

Stephane Landelle created MNG-6785:
--------------------------------------

             Summary: Fail to deploy on Sonatype OSS since maven 3.5.4
                 Key: MNG-6785
                 URL: https://issues.apache.org/jira/browse/MNG-6785
             Project: Maven
          Issue Type: Bug
          Components: Deployment
    Affects Versions: 3.6.2, 3.5.4
         Environment: 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64

openjdk version "1.8.0_202"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_202-b08)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.202-b08, mixed mode)
            Reporter: Stephane Landelle


I've been trying to release AsyncHttpClient for days and deployment was always super slow until it ultimately failed or completely stalled.

The issue seems to be that maven-deploy-plugin wants to upload checksum files. I have no idea where those would come from, as far as I know, those are generated by the maven repository.

 
{code:java}
[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ async-http-client-project ---
Uploading to sonatype-nexus-staging: http://oss.sonatype.org/service/local/staging/deploy/maven2/org/asynchttpclient/async-http-client-project/2.0.40/async-http-client-project-2.0.40.pom
[WARNING] Failed to upload checksum org/asynchttpclient/async-http-client-project/2.0.40/async-http-client-project-2.0.40.pom.sha1: null{code}
 

 

For each actual file, maven-deploy-plugin tries to upload a sha1 and a md5 files and this takes forever to ultimately fail.

I tried upgrading plugins but nothing worked.

I finally found [this ticket|[https://issues.sonatype.org/browse/OSSRH-43371?focusedCommentId=610865&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-610865]] against Sonatype OSS describing the exact same behavior and stating downgrading to maven 3.5.3 fixed the issue.

Indeed, downgrading did the trick!

I'm opening an issue here and not against OSS Sonatype as it looks like a maven regression to me.
 * maven 3.6.2: fails
 * maven 3.5.4: fails
 * maven 3.5.3: works like a charm



--
This message was sent by Atlassian Jira
(v8.3.4#803005)