fix(pacmak): dependency ranges make Maven download too many files#5006
Merged
mergify[bot] merged 2 commits intomainfrom Dec 16, 2025
Merged
fix(pacmak): dependency ranges make Maven download too many files#5006mergify[bot] merged 2 commits intomainfrom
mergify[bot] merged 2 commits intomainfrom
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.
mrgrain
approved these changes
Dec 16, 2025
Contributor
|
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
Contributor
|
Merging (with squash)... |
Contributor
Merge Queue Status✅ The pull request has been merged at 2b13eec This pull request spent 34 minutes 38 seconds in the queue, including 34 minutes 26 seconds running CI. Required conditions to merge
|
Contributor
|
Merging (with squash)... |
rix0rrr
added a commit
that referenced
this pull request
Dec 30, 2025
In #5006 we added a command to make Maven resolve all the wide open version ranges to the latest version, under the motivation that Maven doesn't have a distinction between a dependency declaration file and a lockfile, and ranges don't have the effect that we want (but DO contribute to long build times). In that PR we forgot to pass the settings file that has repository configuration information. Add that.
mergify bot
pushed a commit
that referenced
this pull request
Dec 30, 2025
…gs (#5015) In #5006 we added a command to make Maven resolve all the wide open version ranges to the latest version, under the motivation that Maven doesn't have a distinction between a dependency declaration file and a lockfile, and ranges don't have the effect that we want (but DO contribute to long build times). In that PR we forgot to pass the settings file that has repository configuration information. Add that. --- By submitting this pull request, I confirm that my contribution is made under the terms of the [Apache 2.0 license]. [Apache 2.0 license]: https://www.apache.org/licenses/LICENSE-2.0
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.