[
https://issues.apache.org/jira/browse/MNG-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797238#comment-17797238
]
ASF GitHub Bot commented on MNG-7950:
-------------------------------------
cstamas commented on PR #1337:
URL: https://github.com/apache/maven/pull/1337#issuecomment-1858125936
The goal of this PR is to allow _transparently_ per-session choice of
`VersionScheme`. The "transparently" means that even the constructed object
graph can be retained, as all the selection happens at session runtime, hence
this would work also in mvnd without any extra effort as well. Finally, yes,
this opens ability for users to really shoot themselves in foot (which maven
config does not do that so far?), but I think the benefit of this
> Support new version scheme selector in Maven
> --------------------------------------------
>
> Key: MNG-7950
> URL: https://issues.apache.org/jira/browse/MNG-7950
> 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
>
>
> The generic version scheme is made into component, but it is not enough:
> there should be an indirection and extension point to support multiple
> schemes.
> Resolver introduces MRESOLVER-446 for that.
> There is one component in Maven maven-resolver-provider module that needs to
> be adapted, and use selector instead of ctor passed in scheme.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
