[
https://issues.apache.org/jira/browse/MNG-7951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-7951:
---------------------------------
Description:
-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.
was:
~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 supersedes MNG-7103
Long term plan: this would 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.
> Change resolver provider components to accept version scheme provider
> ---------------------------------------------------------------------
>
> Key: MNG-7951
> URL: https://issues.apache.org/jira/browse/MNG-7951
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-alpha-10
>
>
> -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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
