Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.3.3
-
None
Description
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.
[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
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 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
Attachments
Issue Links
- depends upon
-
HTTPCLIENT-2052 RedirectExec tries to follow redirect even if HttpEntity is non-repeatable
- Closed
-
WAGON-581 Upgrade HttpClient to 4.5.12
- Closed
- relates to
-
WAGON-572 Mark ByteArrayInputStream in WagonHttpEntity as repeatable
- Closed