eliasbalasis

Thanks @martinlippert What I am having in mind is running a set of applications that interact with each other on a remote Docker server over Boot Dashbord to reduce RAM...

Thanks @martinlippert for adding this to 4.12.0.RELEASE Let me know if you need any details.

Are there any plans for this? I suspect further investigation is still required.

Users indeed need to configure both ports. However, the values of such a configuration would be primarily driven by the environment, which is controlled by Maven in our case. I...

I am afraid that the configuration has quite a few moving parts which makes it hard to replicate as part of a sample project. In principle, it is microservice containers...

I agree with @kobynet I have experienced the same issue and I cannot efficiently use parallel builds because the plugin is failing in a non-deterministic fashion. I am also creating...

I am getting the same using Named Locks on Hazelcast, on a Docker container though. -Daether.syncContext.named.factory=semaphore-hazelcast -Daether.syncContext.named.nameMapper=gav I have all the required JARs in "lib/ext" and the Hazelcast configuration in...

FYI. I have discovered that there is probably some problem with the Maven resolver implementation. I initially used apache-maven-3.8.8-resolver-1.9.7 but neither [Redisson](https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html) nor [Hazelcast](https://maven.apache.org/resolver/maven-resolver-named-locks-hazelcast/index.html) worked. Now I am using apache-maven-3.8.8-resolver-1.8.2...

> Windows Filesystem and file-locking is a disaster I couldn't agree more. > the error does not occur even not when I run parallel builds Trust me, it is purely...

This is a very good direction. I have witnessed locking failures on larger projects even with Redisson and Hazelcast (as mentioned in the past). These are probably timeouts in which...