[
https://issues.apache.org/jira/browse/MNG-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343764#comment-15343764
]
ASF GitHub Bot commented on MNG-6049:
-------------------------------------
Github user talios commented on the issue:
https://github.com/apache/maven/pull/70
@barthel Maybe, I'm running 3.4.0-SNAPSHOTs anyway, and might pull in your
PR to play with and see if it helps with what I'm doing. My currently problem
is that IntelliJ IDEA doesn't seem to execute any lifecycle extensions, so
things that affect dependency resolution don't get reflected in IntelliJ ( my
process is currently injecting user properties, but I suspect a pluggable
dependency selector may also not get picked up ).
> 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)
