apache / apache/maven

[MNG-7951] Change resolver provider components to accept version scheme provider

Open
#8,963 1 comment 0 reactions 1 assignee Claimed by @cstamas View on GitHub
maintenance priority:major
Dominant language
Java
Stars
5.3k
Forks
3.1k
Avg merge
20h 42m
Merged PRs (30d)
297

Description

**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MNG-7951](https://issues.apache.org/jira/browse/MNG-7951?redirect=false)** and commented

-Resolver implemented MRESOLVER-446 and there is one component in maven-resolver-provider that needs change to have Maven fully support per-session VersionScheme. Also we should look for any other possible spots as well...-

This also follows up on MNG-7103

Long term plan: allow us to kill off Maven Version implementations, possibly reimplementing it as resolver' VersionScheme (it is nicely UT covered) with all it's flaws, and then have explicit switch between "legacy" (Maven Version) and "generic" (Resolver) version scheme, or maybe even have some new future schemes as well.

---

**Issue Links:**
- [MRESOLVER-446](https://issues.apache.org/jira/browse/MRESOLVER-446) Version Scheme Provider
(_**"is a child of"**_)
- [MNG-7103](https://issues.apache.org/jira/browse/MNG-7103) Make generic VersionScheme a component
(_**"supercedes"**_)

**Remote Links:**
- [GitHub Pull Request #1337
](https://github.com/apache/maven/pull/1337)
- [GH PR #1337
](https://github.com/apache/maven/pull/1337)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.