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/05/26 09:54:00 UTC

[jira] [Created] (MRESOLVER-364) Revert MRESOLVER-132

Tamas Cservenak created MRESOLVER-364:
-----------------------------------------

             Summary: Revert MRESOLVER-132
                 Key: MRESOLVER-364
                 URL: https://issues.apache.org/jira/browse/MRESOLVER-364
             Project: Maven Resolver
          Issue Type: Task
            Reporter: Tamas Cservenak


Revert this commit [https://github.com/apache/maven-resolver/commit/fcb6be59c5a5855573886b09c70dab80074a1d27]

Must be done manually, as since then class was made into component and this filename is an interface now.

Reasoning: as we recently saw, they may be still plugins (knowingly or not knowingly) using maven-compat, that update check manager read/writes same files as resolve (but uses different keys). This lock was in place way long before SyncContext, and intent was to sync resolver and maven-compat access, that still happens, so undo this change.



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