maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MNG-6049) Add behavior to filter resolved version ranges of an artifact
Date Wed, 22 Jun 2016 06:01:07 GMT


ASF GitHub Bot commented on MNG-6049:

Github user talios commented on the issue:
    @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:
>             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

View raw message