Feat: Version range filters plus - #11955
Merged
cstamas merged 12 commits intoApr 21, 2026
Merged
Conversation
Builds upon incoming Resolver 2 features. Vastly improves range filter support.
…x-versionrangefilters-plus
cstamas
changed the title
…x-versionrangefilters-plus
cstamas
marked this pull request as ready for review
April 17, 2026 17:55
…x-versionrangefilters-plus
And anything else that performs collection/resolution, but NOT to: * plugins * build extensions * core extensions
cstamas
changed the title
…x-versionrangefilters-plus
Member
Author
|
Anyone? |
…x-versionrangefilters-plus
Member
Author
|
Resolver 2.0.17 has all changes merged in and Jenkins did deploy latest snapshot of it. Merged |
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.
Builds upon incoming Resolver 2 features. Vastly improves range filter support. Contains upgrade to Resolver 2.0.17 and needed changes too (internals/test in maven-compat).
The filtering is applied to project dependencies only, and anything else (ie a plugin) that programmatically performs collection/resolve using Resolver in Maven.
Ranges are not applied to: