Ability to augment metadata nature for version range request #1518
Conversation
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
The idea is to let caller be able to augment the nature of metadata to resolve version range from. Resolver already handles this, and is more elegant, than to have caller fiddle with filtering the remote repositories or alike. Also, this way client code (ie. Maven) can expose more fine grained configuration for this.
cstamas
added a commit
to cstamas/maven
that referenced
this pull request
Jul 4, 2025
Ability to control which repositories to be queried to resolve ranges. Introduced new property: `maven.versionRangeResolutionNature` that is used in VersionRangeResolver, and mean: * not set; behave as before (default) * "auto" string; will check lower and upper bounds, and if any is snapshot, will querty snapshot reposes otherwise not * any valid value of resolver Metadata.Nature enum; then will use that Depends on apache/maven-resolver#1518
slawekjaranowski
approved these changes
Jul 6, 2025
|
@cstamas Please assign appropriate label to PR according to the type of change. |
|
@cstamas The PR can't be associated to a milestone, because there are multiple open milestones. Please add the text "branch: maven-resolver-1.9.x" to the description to the milestone where this PR belongs to. |
|
This will need Maven changes once this version is integrated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The idea is to let caller be able to augment the nature of metadata to resolve version range from.
Resolver already handles this, and is more elegant, than to have caller fiddle with filtering the remote repositories or alike. Also, this way client code (ie. Maven) can expose more fine grained configuration for this.