[
https://issues.apache.org/jira/browse/MRESOLVER-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MRESOLVER-364:
--------------------------------------
Component/s: Resolver
> Revert MRESOLVER-132
> --------------------
>
> Key: MRESOLVER-364
> URL: https://issues.apache.org/jira/browse/MRESOLVER-364
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: 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)
