You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2022/10/20 08:11:02 UTC
[jira] [Updated] (MNG-7103) Make generic VersionScheme a component
[ https://issues.apache.org/jira/browse/MNG-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated MNG-7103:
---------------------------------
Fix Version/s: 4.0.0-alpha-2
> Make generic VersionScheme a component
> --------------------------------------
>
> Key: MNG-7103
> URL: https://issues.apache.org/jira/browse/MNG-7103
> Project: Maven
> Issue Type: Task
> Components: Core
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-alpha-1, 4.0.0-alpha-2, 4.0.0
>
>
> Maven Resolver, while provides {{VersionScheme}} implementation (the {{GenericVersionScheme}} does not binds it (makes it a component) nor creates instance from it (it works against interfaces, actual implementation is left to "integration" like Maven is).
> As Maven is the main "user" of GenericVersionScheme, it makes sense to bind it in Maven Realm.
> Right now, instances of it are created "ad-hoc" (wherever needed) instead of being injected (and shared as singleton), as implementation is stateless/thread-safe.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)