GH-4185: Manage version of jspecify directly - #4186
Open
afs wants to merge 1 commit into
Open
Conversation
afs
force-pushed
the
exclude-jspecify
branch
from
September 1, 2026 12:41
d10912d to
f4309bd
Compare
afs
changed the title
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
1 participant
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.
GitHub issue resolved #4185
Exclude jspecify: it can can cause maven version convergence problems.
It is not required at run time.
Caveat: I am currently having problems with the build at the point of downloading corepack.That happens after version convergence has succeeded so I don't think it is related.
It may not affect this PR -- github builds see different caches.
By submitting this pull request, I acknowledge that I am making a contribution to the Apache Software Foundation under the terms and conditions of the Contributor's Agreement.