cstamas commented on code in PR #185: URL: https://github.com/apache/maven-resolver/pull/185#discussion_r904095056
########## maven-resolver-named-locks/src/site/markdown/index.md.vm: ########## @@ -52,8 +56,7 @@ Finally, "distributed" named lock implementations are the following (separate mo - `semaphore-hazelcast-client` implemented in `org.eclipse.aether.named.hazelcast.HazelcastClientCPSemaphoreNamedLockFactory`. - `semaphore-hazelcast` implemented in `org.eclipse.aether.named.hazelcast.HazelcastCPSemaphoreNamedLockFactory`. -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! +Sharing a local repository between multiple hosts (i.e., on a busy CI server) requires a distributed named lock! Review Comment: Agreed, but that's actually the point as well: they do not recommend as Maven had issues with it before resolver 1.7 :wink: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
