[
https://issues.apache.org/jira/browse/MRESOLVER-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17226922#comment-17226922
]
Tamás Cservenák edited comment on MRESOLVER-145 at 11/5/20, 6:45 PM:
---------------------------------------------------------------------
[https://github.com/apache/maven-resolver/pull/77]
The PR adds a "pluggable" synccontext implementation (backed by JVM Semaphore
and JVM ReadWriteLock, Hazelcast and Redisson – code copied from existing
redisson synccontext implementation).
I'd propose a "followup" issue, to drop "maven-resolver-synccontext-global" and
maybe "maven-resolver-synccontext-redisson" modules as well, if testing proves
"maven-resolver-synccontext-named" redisson implementation as an equivalent
replacement.
was (Author: cstamas):
[https://github.com/apache/maven-resolver/pull/77]
The PR adds a "pluggable" synccontext implementation (backed by JVM Semaphore
and JVM ReadWriteLock, Hazelcast and Redisson – code copied from existing
redisson synccontext implementation).
I'd propose a "followup" issue, to drop "global" and maybe "redisson" modules
as well, if testing proves named redisson an equivalent replacement.
> Introduce more SyncContext implementations
> ------------------------------------------
>
> Key: MRESOLVER-145
> URL: https://issues.apache.org/jira/browse/MRESOLVER-145
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
> Reporter: Tamás Cservenák
> Assignee: Michael Osipov
> Priority: Minor
>
> Aside of existing "global" (too coarse, not really usable) and "redisson"
> sync context implementations, we may try out more implementations and maybe
> even benchmark/compare them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
