chore(java-devel): Tweak Maven transport settings [skip ci] - #1584
Merged
Conversation
Techassi
changed the title
lfrancke
reviewed
Jul 20, 2026
sbernauer
reviewed
Jul 20, 2026
Co-authored-by: Sebastian Bernauer <sebastian.bernauer@stackable.tech>
Techassi
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
sbernauer
approved these changes
Jul 20, 2026
sbernauer
left a comment
sbernauer
left a comment
Member
There was a problem hiding this comment.
Let's see if that improves things...
Techassi
enabled auto-merge
July 20, 2026 12:20
Techassi
disabled auto-merge
July 20, 2026 12:20
Member
Author
|
Let's wait with merging this until (hopefully) we can finish building the rc1 images. |
Techassi
changed the title
Member
Author
|
All rc1 images (except a single Superset image) built. I marked this PR with |
Techassi
moved this from Development: In Review
to Development: Done
in Stackable Engineering
lfrancke
added a commit
that referenced
this pull request
Jul 21, 2026
…ed by Maven 3.9 #1584 added HTTP retry settings (retryHandler.count/interval/intervalMax) under the aether.transport.http.* keys. That prefix is the maven-resolver 2.x / Maven 4 spelling; we build with Maven 3.9.16 (maven-resolver 1.9.27), which only reads aether.connector.http.*, so those settings currently have no effect. Add the connector.* spelling alongside the transport.* one so the retries actually apply today, mirroring how connectionMaxTtl is already dual-spelled. CI Maven failures are connection-level (stale keep-alive connections dropped by the network; no server-side 5xx in Nexus/Apache logs). maven-resolver's retry handler retries these IOExceptions, so this makes the intended retry behaviour effective. Key names verified against ConfigurationProperties.java @ maven-resolver-1.9.27.
lfrancke
added a commit
that referenced
this pull request
Jul 21, 2026
…ed by Maven 3.9 #1584 added HTTP retry settings (retryHandler.count/interval/intervalMax) under the aether.transport.http.* keys. That prefix is the maven-resolver 2.x / Maven 4 spelling; we build with Maven 3.9.16 (maven-resolver 1.9.27), which only reads aether.connector.http.*, so those settings currently have no effect. Add the connector.* spelling alongside the transport.* one so the retries actually apply today, mirroring how connectionMaxTtl is already dual-spelled. CI Maven failures are connection-level (stale keep-alive connections dropped by the network; no server-side 5xx in Nexus/Apache logs). maven-resolver's retry handler retries these IOExceptions, so this makes the intended retry behaviour effective. Key names verified against ConfigurationProperties.java @ maven-resolver-1.9.27.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This might get cherry-picked onto the
release-26.7branch to potentially help with failing builds in CI.This PR tweaks various Maven transport/resolver settings to be a little more network failure resistant in the future. These network issues seem to be known by the Java/Maven community and are related to Azure's network setup.