slachiewicz opened a new pull request, #2298: URL: https://github.com/apache/maven-resolver/pull/2298
`IpcNamedLock.doLockExclusively` threw `LockUpgradeNotSupportedException` whenever any shared step was on the thread's stack, so exclusive → shared → exclusive failed. The file, read-write and semaphore based locks allow it: the exclusive lock is still held, so nothing is upgraded, and only a shared-only stack is an upgrade. The IPC lock now applies the same rule. `wrwBoxing` in the lock test supports covers the named-locks factories and, through `IpcNamedLockFactoryIT`, the IPC factory; without the change the IPC run fails with `LockUpgradeNotSupportedException`. The Hazelcast and Redisson test-support copies are not touched; their locks already pass the equivalent check in `AdaptedSemaphoreNamedLock`. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
