[
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343730#comment-15343730
]
ASF GitHub Bot commented on MNG-6049:
-------------------------------------
Github user talios commented on the issue:
https://github.com/apache/maven/pull/70
@barthel is there an example anywhere of using this? I have a project
(custom lifecycle extension) myself where I think utilizing this will actually
make what I'm doing much easier, nicer, and probably more "maven safe".
> 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)
