Task List

• Steps to reproduce provided
• Stacktrace (if present) provided
• Example that reproduces the problem (link to git repository is ideal)
• Full description of the issue provided (see below)

Steps to Reproduce

I'm afraid the issue isn't reliably reproducable.

I just ran jreleaserDeploy and it failed. The deployment bundle was uploaded, though, and in state "VALIDATED" in the Central portal.

Output from failed build:

[INFO]  Deploying Maven artifacts
[INFO]    [maven] Deploying all staged artifacts
[INFO]      [mavenCentral] Deploying to artifacts
[INFO]      [mavenCentral] Verifying prerequisites
[INFO]      [mavenCentral]  - org.junit-junit-framework-5.13.2-bundle.zip
[INFO]      [mavenCentral] Uploading org.junit-junit-framework-5.13.2-bundle.zip
[INFO]  Writing output properties to build/jreleaser/output.properties
[ERROR] JReleaser failed after 9.302 s

Build Scan (with stacktrace): https://ge.junit.org/s/ty5gxju2meksy/failures#1

Resulting build/jreleaser/output.properties (notably missing deployMavenCentralArtifactsDeploymentId):

#JReleaser 1.18.0
#Tue Jun 24 14:21:34 CEST 2025
deployMavenCentralArtifactsNamespace=org.junit
javaVendor=Eclipse Adoptium
javaVersion=21.0.7
javaVmVersion=21.0.7+6-LTS
platform=linux-x86_64
platformReplaced=linux-x86_64
projectName=junit-framework
projectSnapshot=false
projectVersion=5.13.2
projectVersionMajor=5
projectVersionMinor=13
projectVersionNumber=5.13.2
projectVersionPatch=2
timestamp=2025-06-24T14\:21\:24.016147285+02\:00

Expected Behaviour

It shouldn't fail. 🙂

Actual Behaviour

Since MavenCentral.waitForState is on the stacktrace, I suspect it's that API call which receives the 404. It seems there's a delay after uploading until the status can be queried?

Environment Information

• Operating System: Linux
• JReleaser Version: 1.18.0
• JDK Version: 21

Please paste stacktraces from [out|build|target]/jreleaser/trace.log.