[
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6049.
-------------------------------
Resolution: Fixed
Fixed with
[1b2451e7949dbb68df5bb973742d9a9a0e84f629|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=1b2451e7949dbb68df5bb973742d9a9a0e84f629]
and
[a2777f15199514c32862e96f22d8e6e2864f149d|https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=a2777f15199514c32862e96f22d8e6e2864f149d].
> 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)
