[
https://issues.apache.org/jira/browse/MRESOLVER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-342:
--------------------------------------
Description:
Lift and integrate mvnd IPC locking as new named lock (or for perf reason, to
lessen outbound calls, as another SyncContext) implementation into resolver. It
is MP capable, but probably a bit slower than file locking.
For some "weird" environments (like WSL2) we could make use of this (slower but
potentially supported) locking tech.
Ref:
[https://github.com/apache/maven-mvnd/tree/0.7.1/sync/src/main/java/org/mvndaemon/mvnd/sync]
was:
Lift and integrate mvnd IPC locking as new named lock implementation into
resolver. It is MP capable, but probably a bit slower than file locking.
For some "weird" environments (like WSL2) we could make use of this (slower but
potentially supported) locking tech.
Ref:
[https://github.com/apache/maven-mvnd/tree/0.7.1/sync/src/main/java/org/mvndaemon/mvnd/sync]
> New named lock: IPC
> -------------------
>
> Key: MRESOLVER-342
> URL: https://issues.apache.org/jira/browse/MRESOLVER-342
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
>
> Lift and integrate mvnd IPC locking as new named lock (or for perf reason, to
> lessen outbound calls, as another SyncContext) implementation into resolver.
> It is MP capable, but probably a bit slower than file locking.
> For some "weird" environments (like WSL2) we could make use of this (slower
> but potentially supported) locking tech.
> Ref:
> [https://github.com/apache/maven-mvnd/tree/0.7.1/sync/src/main/java/org/mvndaemon/mvnd/sync]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
