Skip to content

Clarify file-lock being a distributed name lock #184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kwin wants to merge 1 commit into from
Closed

Clarify file-lock being a distributed name lock #184

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions maven-resolver-named-locks/src/site/markdown/index.md.vm
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
Expand All @@ -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:
Expand Down