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

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/05/01 09:51:00 UTC

[jira] [Updated] (MRESOLVER-175) Drop SyncContextFactory delegates in favor of a selector approach

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

Michael Osipov updated MRESOLVER-175:
-------------------------------------
    Summary: Drop SyncContextFactory delegates in favor of a selector approach  (was: Drop syncContextFactory delegates in favor of a selector approach)

> Drop SyncContextFactory delegates in favor of a selector approach
> -----------------------------------------------------------------
>
>                 Key: MRESOLVER-175
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-175
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Michael Osipov
>            Assignee: Tamás Cservenák
>            Priority: Major
>             Fix For: 1.7.0
>
>
> Drop all the factory delegates, leave only named SyncContextFactory
> as only factory, but extend it to be able to functionally replace
> the dropped ones.
> Replacements:
>     Introduced NoopNamedLockFactory
>     GlobalSyncContextFactory becomes combo of static NameMapper + any NamedLockFactory
>     NoLockSyncContextFactory becomes combo of any NameMapper + NoopNamedLockFactory



--
This message was sent by Atlassian Jira
(v8.3.4#803005)