janhoy opened a new pull request, #4140:
URL: https://github.com/apache/solr/pull/4140
Spinoff from #4098
With help of Claude Code, here is a custom version alignment configuration
that ensures that
1. Standard java configs use
`consistentResolution.useCompileClasspathVersions()`
2. Custom packaging configs (`runtimeLibs`, `solrPlatformLibs`) align with
`runtimeClasspath` versions
3. Validation configs (`jarValidation`) align runtimeClasspath versions
So this means all these will be the same:
- compileClasspath
- runtimeClasspath
- testCompileClasspath
- testRuntimeClasspath
- runtimeLibs
- solrPlatformLibs
- jarValidation
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-core` in
`s3-repository`.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
