fix(java-runtime): dependency ranges make Maven download too many files#5005
Merged
fix(java-runtime): dependency ranges make Maven download too many files#5005
Conversation
Given a dependency version range, Maven will download metadata for all possible versions before every (uncached) build. This takes a long time, before finally resolving to the latest version anyway. Instead, we use the Maven 'versions' plugin to resolve our wide ranges to point versions. We want the "latest matching" version anyway, and if we don't the resolution now (which downloads the .poms of all possible versions) it will happen during every single build.
leonmk-aws
approved these changes
Dec 22, 2025
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.
Given a dependency version range, Maven will download metadata for all possible versions before every (uncached) build. This takes a long time, before finally resolving to the latest version anyway.
Instead, we use the Maven 'versions' plugin to resolve our wide ranges to point versions. We want the "latest matching" version anyway, and if we don't the resolution now (which downloads the .poms of all possible versions) it will happen during every single build.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.