[ https://issues.apache.org/jira/browse/MNG-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805501#comment-17805501 ]
ASF GitHub Bot commented on MNG-7960: ------------------------------------- cstamas commented on code in PR #1353: URL: https://github.com/apache/maven/pull/1353#discussion_r1448657055 ########## pom.xml: ########## @@ -176,7 +176,7 @@ under the License. <plexusInterpolationVersion>1.26</plexusInterpolationVersion> <plexusTestingVersion>1.0.0</plexusTestingVersion> <plexusXmlVersion>4.0.1</plexusXmlVersion> - <resolverVersion>2.0.0-alpha-5</resolverVersion> + <resolverVersion>2.0.0-alpha-6</resolverVersion> Review Comment: There is a separate PR just for the update https://github.com/apache/maven/pull/1373 (and removal of some deprecation warnings in tests) > Artifact collection filtering > ----------------------------- > > Key: MNG-7960 > URL: https://issues.apache.org/jira/browse/MNG-7960 > Project: Maven > Issue Type: New Feature > Components: Artifacts and Repositories > Reporter: Tamas Cservenak > Assignee: Tamas Cservenak > Priority: Major > Fix For: 4.0.0, 4.0.0-alpha-11 > > > Exposed work from MRESOLVER-451 and MRESOLVER-460: allow for various > filterings. > User should be able to "tune" range processing. Also, as this affects > resolution, ideally these "tuned" parameters should be stored along project, > especially if project relies on these (ie. in {{.mvn/maven.config}}). > Explanation: Maven is notoriously "bad" when ranges are being used. Hence, > this issue introduces (range) version filtering support. The configuration > accepts an "expression" (CSV) of filters. Supported filters are: > * "h" (equivalent of "h(1)") or "h(N)" - that selects "top N" versions from > range > * "l" (equivalent of "l(1)") or "l(N)" - that selects "bottom N" versions > from range > * "s" snapshot filter: if root/project is snapshot, will allow snapshots in > ranges, otherwise snapshot versions are filtered out (also see Resolver > config {{aether.snapshotFilter}} present in Resolver 1.x but has no effect in > Maven3 as it is not used). > * "e(G:A:V)" exclusion, if range for G:A is processed, V is _excluded_ from > range. V can be version range as well, then whole range is excluded. > The built expressions are evaluated in-order, and filtering effect is > accumulated. Hence, expression like "h(5),l" will return 5th highest version, > etc. > This depends on resolver release. -- This message was sent by Atlassian Jira (v8.20.10#820010)