arturobernalg commented on issue #11116: URL: https://github.com/apache/maven/issues/11116#issuecomment-6263926910
Same root issue as #9049, where this is cross-linked. I reproduced the before/after with a standalone program using `NamedLockFactoryAdapter` directly (one thread holding the lock, another timing out on it), not just by reading the diff: - maven-resolver 1.9.22 (what Maven 3.9.9 depends on): default timeout 30s, exception message is exactly `Could not acquire lock(s)`. - - maven-resolver 2.0.24: default timeout 900s, message names the blocked artifact and suggests the `aether.syncContext.named.time` property. This is `cstamas`'s fix (maven-resolver#1644, backported to 1.9.x in maven-resolver#1662, first released as 1.9.25). I checked the released Maven poms: Maven 3.9.16 already depends on resolver 1.9.27, which has this, so a build on a current 3.9.x release should no longer hit the bare 30-second timeout or the unhelpful message, even though the deeper cause of slow lock acquisition under I/O pressure is unrelated and still open. -- 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]
