[
https://issues.apache.org/jira/browse/MRESOLVER-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726571#comment-17726571
]
Tamas Cservenak edited comment on MRESOLVER-364 at 5/26/23 10:08 AM:
---------------------------------------------------------------------
Yes, if we'd be 100% there is no possibility for this to happen. But we KNOW
that is not the case,
For example today, it is enough to use versions-maven-plugin 2.12 that is not
so old even (current today is 2.15)
was (Author: cstamas):
Yes, if we'd be 100% there is no possibility for this to happen. But we KNOW
that is not the case,
> 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)
