[ 
https://issues.apache.org/jira/browse/MNG-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952723#comment-16952723
 ] 

Michael Osipov commented on MNG-6785:
-------------------------------------

Alright, the checksum will do the  
[https://github.com/apache/maven-resolver/blob/master/maven-resolver-connector-basic/src/main/java/org/eclipse/aether/connector/basic/BasicRepositoryConnector.java#L610-L619|following]
 which will result in a 
[https://github.com/apache/maven-resolver/blob/master/maven-resolver-spi/src/main/java/org/eclipse/aether/spi/connector/transport/PutTask.java#L60-L67|{{ByteArrayInputStream}}]
 and the intended to be 
[https://github.com/apache/maven-resolver/blob/master/maven-resolver-transport-wagon/src/main/java/org/eclipse/aether/transport/wagon/WagonTransporter.java#L655-L680|streamed].
 {{AbstractHttpClientWagon}} has its own {{HttpEntity}} impl which will mark it 
as non-repeatable as soon as in {{InputStream}} is passed.

I will add some debug some to prove my assumption. There are several ways to 
fix this, but one -- imho -- w/o changing the API.

> 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.5.4, 3.6.2
>         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
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> 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)

Reply via email to