[
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343726#comment-15343726
]
Uwe Barthel commented on MNG-6049:
----------------------------------
This solution was initially developed in MNG-3092.
There is a lot communication about it in MNG-3092 and in the [pull request on
github.com|https://github.com/apache/maven/pull/70].
It doesn't _solve_ the MNG-3092, but it is a part of a solution. Therefore this
new issue was created.
See original suggestion of [~michael-o]:
{quote}
I am already working on your PRs. I think, committing this under MNG-3092 is
wrong and will explain why. I we cannot close the issue, people won't see this
in the changelog. They won't simply know that a simple extension can solve
their problem. Can you create a separate issue for your solution and make
MNG-3092 depend on your issue? People would then know that they can solve it by
adding an extension.
{quote}
> 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
> Assignee: Michael Osipov
> Priority: Critical
> Fix For: 3.4.0
>
>
> 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
(v6.3.4#6332)
