jianguotian opened a new pull request, #56: URL: https://github.com/apache/paimon-mosaic/pull/56
Every release.yml run for 0.1.0 (rc1, rc2 ×5 retries, rc3, and the v0.1.0 final tag — 7 total) failed at the same step with HTTP 502 from repository.apache.org on the jar PUT, including the v0.1.0 final tag run on 2026-06-03. The jar on Maven Central had to be uploaded out of band. The retry added in #44 walks all 10 attempts and every one returns 502, so the failure is not transient. The underlying maven-deploy-plugin 2.8.2 from Apache Parent POM v23 uses the Maven Wagon HTTP transport, whose PUT for the jar artifact is rejected by the Apache Nexus reverse proxy. Replacing the deploy execution with nexus-staging-maven-plugin 1.7.0 (extensions=true) routes the upload through Sonatype's own HttpClient-based transport and gathers artifacts into a local staging directory before pushing them atomically. The same plugin is used by other Apache projects against repository.apache.org without 502s. autoReleaseAfterClose=false preserves the existing manual gate: the release manager still closes and releases the staging repository via the Nexus UI after the vote passes. Drops -DretryFailedDeploymentCount and -Daether.connector.basic.parallelPut from the workflow as both only apply to the vanilla deploy plugin. Verified locally with mvn help:effective-pom: Maven reports "1 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin". The release-version code path activates "Performing local staging" and then attempts the Nexus REST handshake (fails on local with "Server credentials not found", as expected without LDAP credentials). Cannot validate the actual upload locally without committer credentials; ready for a smoke deploy from any committer (mvn deploy -Prelease -DskipTests against repository.apache.org) before merging. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
