You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/12/16 19:15:00 UTC

[jira] [Closed] (MRESOLVER-457) Revert MRESOLVER-446

     [ https://issues.apache.org/jira/browse/MRESOLVER-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak closed MRESOLVER-457.
-------------------------------------
    Resolution: Fixed

> Revert MRESOLVER-446
> --------------------
>
>                 Key: MRESOLVER-457
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-457
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 2.0.0-alpha-6
>
>
> Revert MRESOLVER-446 as it is not needed. Supplier (and Maven) can customize as all places where VersionScheme needed, is client injected/set (like on request or so).
> Moreover, in Resolver 2 one needs to construct RepoSystem (DI complete component graph) -> to create session -> that can be used with selector to select VersionScheme -> that in turn is NEEDED in component graph. This is a cycle as this.
> With selector this was somewhat solved, but there are components that have no access to RepoSysSession... and those are the problem. IF all Sisu components would have access to RepoSysSession, this cycle could be broken easily.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)