Tamas Cservenak created MRESOLVER-373:
-----------------------------------------
Summary: Partially undo MRESOLVER-346
Key: MRESOLVER-373
URL: https://issues.apache.org/jira/browse/MRESOLVER-373
Project: Maven Resolver
Issue Type: Task
Components: Resolver
Reporter: Tamas Cservenak
Fix For: 1.9.13
The change done in MRESOLVER-346 in relation to DefaultArtifactResolver and
DefaultMetadataResolver is wrong, and is actually complemented by
MRESOLVER-349, so is really not needed. The change happened for DefaultDeployer
is correct.
In short, DefaultArtifactResolver within syncContext will invoke
DefaultMetadataResolver that may case "lock upgrade" attempt that is NOT
supported by named locks -> failure.
Just undo the change and make two component as before, always use exclusive
locks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
