From d605645dc7c93a8e2f8f79c2f3ac8db667c23b90 Mon Sep 17 00:00:00 2001 From: Konrad Windszus Date: Wed, 22 Jun 2022 17:07:19 +0200 Subject: [PATCH] Clarify `file-lock` being a distributed name lock --- maven-resolver-named-locks/src/site/markdown/index.md.vm | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/maven-resolver-named-locks/src/site/markdown/index.md.vm b/maven-resolver-named-locks/src/site/markdown/index.md.vm index 0d8d40166..58cd16ab4 100644 --- a/maven-resolver-named-locks/src/site/markdown/index.md.vm +++ b/maven-resolver-named-locks/src/site/markdown/index.md.vm @@ -31,12 +31,12 @@ Out of the box, "local" (local to JVM) named lock implementations are the follow JVM `java.util.concurrent.locks.ReentrantReadWriteLock`. - `semaphore-local` implemented in `org.eclipse.aether.named.providers.LocalSemaphoreNamedLockFactory` that uses JVM `java.util.concurrent.Semaphore`. -- `file-lock` implemented in `org.eclipse.aether.named.providers.FileLockNamedLockFactory` that uses - JVM `java.nio.channels.FileLock`. - `noop` implemented in `org.eclipse.aether.named.providers.NoopNamedLockFactory` that uses no locking. -Out of the box, "distributed" named lock implementations are the following (separate modules which require additional dependencies): +Out of the box, "distributed" named lock implementations are the following (all apart from the first are separate modules which require additional dependencies): +- `file-lock` implemented in `org.eclipse.aether.named.providers.FileLockNamedLockFactory` that uses + [JVM `java.nio.channels.FileLock`](https://docs.oracle.com/javase/8/docs/api/java/nio/channels/FileLock.html). - `rwlock-redisson` implemented in `org.eclipse.aether.named.redisson.RedissonReadWriteLockNamedLockFactory`. - `semaphore-redisson` implemented in `org.eclipse.aether.named.redisson.RedissonSemaphoreNamedLockFactory`. - `semaphore-hazelcast-client` implemented in `org.eclipse.aether.named.hazelcast.HazelcastClientCPSemaphoreNamedLockFactory`. @@ -45,7 +45,6 @@ Out of the box, "distributed" named lock implementations are the following (sepa Local named locks are only suited within one JVM with a multithreaded build. Sharing a local repository between multiple Maven processes (i.e., on a busy CI server) requires a distributed named lock! - The aforementioned (opaque) IDs need to be mapped from artifacts and metadata. Out of the box, name mapper implementations are the following: