[
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939818#comment-17939818
]
Guillaume Nodet edited comment on MNG-6049 at 3/31/25 9:32 PM:
---------------------------------------------------------------
AFAIK, this has been implemented and is now configurable using
{{{}maven.session.versionFilter{}}}, introduced in 4-alpha-12, see
[https://maven.apache.org/ref/4-LATEST/maven-configuration.html]
was (Author: gnt):
AFAIK, this has been implemented and is now configurable using
{{{}maven.session.versionFilter{}}}, see
[https://maven.apache.org/ref/4-LATEST/maven-configuration.html]
> Add behavior to filter resolved version ranges of an artifact
> -------------------------------------------------------------
>
> Key: MNG-6049
> URL: https://issues.apache.org/jira/browse/MNG-6049
> Project: Maven
> Issue Type: Improvement
> Components: Core, Dependencies
> Reporter: Uwe Barthel
> Priority: Critical
> Fix For: 4.x / Backlog
>
>
> The discussion on issue MNG-3092 shows the seriously needs of different kinds
> of version range resolving in Maven.
> This solution provides a hook for Maven extensions/plugins to change the list
> of resolved version range results as required.
> The {{DefaultVersionRangeResolver}} will be extended with a filter for
> version range results. A new interface {{VersionRangeResultFilter}} is added
> and a non-filtering {{DefaultVersionRangeResultFilter}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
