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

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/05/26 09:58:00 UTC

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

    [ https://issues.apache.org/jira/browse/MRESOLVER-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726568#comment-17726568 ] 

Michael Osipov commented on MRESOLVER-364:
------------------------------------------

So without Maven Compat this revert would not be necessary?

> Revert MRESOLVER-132
> --------------------
>
>                 Key: MRESOLVER-364
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-364
>             Project: Maven Resolver
>          Issue Type: Task
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 1.9.11
>
>
> Revert MRESOLVER-132 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)