You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/06/30 17:51:00 UTC

[jira] [Created] (MRESOLVER-381) Undo MRESOLVER-373 as it was fixed by other means

Tamas Cservenak created MRESOLVER-381:
-----------------------------------------

             Summary: Undo MRESOLVER-373 as it was fixed by other means
                 Key: MRESOLVER-381
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-381
             Project: Maven Resolver
          Issue Type: Task
            Reporter: Tamas Cservenak
             Fix For: 1.9.14


The MRESOLVER-373 made two important operations serialized (again, since existence of locks), but the proper fix was actually this one (also part of MRESOLVER-373):
https://github.com/apache/maven-resolver/commit/4fb1cf93b478ab1eeb563c3e69ad888017265e54

And given that artifacts and metadata does not use same lock name, the code undone would work. Still, errors would occur again, with "static" name mapper (maps always to same name), hence some smarter change is needed: when artifact resolver invokes metadata resolver, maybe it needs to unlock and then invoke?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)