[
https://issues.apache.org/jira/browse/MNG-7950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797232#comment-17797232
]
ASF GitHub Bot commented on MNG-7950:
-------------------------------------
gnodet commented on PR #1337:
URL: https://github.com/apache/maven/pull/1337#issuecomment-1858101613
I'm not sure I'm buying the use of the additional indirection for the
`VersionSchemeSelector`. I wonder if it would be just as simple to be injected
with a `VersionScheme`. If users want to use a different scheme, they just
need to register one with a higher `@Priority`. And if we want pluggability,
we could also define a `@SessionSCoped` component that would delegate to the
`VersionSchemeSelector` underneath.
But at least, components would simply be injected with a single
`VersionScheme`.
> 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)
