Explicit version alignment between gradle configurations#4140
Draft
janhoy wants to merge 1 commit intoapache:mainfrom
Draft
Explicit version alignment between gradle configurations#4140janhoy wants to merge 1 commit intoapache:mainfrom
janhoy wants to merge 1 commit intoapache:mainfrom
Conversation
github-actions
bot
added
dependencies
dsmiley
reviewed
Feb 17, 2026
Contributor
dsmiley
left a comment
dsmiley
left a comment
There was a problem hiding this comment.
Thanks for picking this up!
| solrPlatformLibs | ||
| solrPlatformLibs { | ||
| resolutionStrategy { | ||
| preferProjectModules() |
Contributor
There was a problem hiding this comment.
I read the docs but it's not clear how this is relevant to us
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
2 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.
Spinoff from #4098
With help of Claude Code, here is a custom version alignment configuration that ensures that
consistentResolution.useCompileClasspathVersions()runtimeLibs,solrPlatformLibs) align withruntimeClasspathversionsjarValidation) align runtimeClasspath versionsSo this means all these will be the same:
Sometimes this causes an older lib version to be chosen, if compile/runtime was resolved to that version for some reason. But I believe it is better to align them all than to risk packaging different versions in tarball than what is being run in tests?
Looking at the re-generated lockfiles in the PR there is much more alignment, but still some places with a diff, such as
woodstox-coreins3-repository.