[
https://issues.apache.org/jira/browse/MRESOLVER-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735244#comment-17735244
]
ASF GitHub Bot commented on MRESOLVER-373:
------------------------------------------
cstamas opened a new pull request, #303:
URL: https://github.com/apache/maven-resolver/pull/303
This class currently gives away same names for artifact and metadata locks,
that causes MRESOLVER-373 where artifact and metadata resolver together attempt
illegal "lock upgrade", as both operate on same named lock.
This is wrong, as all other name mappers distinguish among them, also in
case of snapshots, there are cases when shared lock is enough for artifact but
metadata MAY need refresh, hence exclusive.
---
https://issues.apache.org/jira/browse/MRESOLVER-373
> Remove lock upgrading code
> --------------------------
>
> Key: MRESOLVER-373
> URL: https://issues.apache.org/jira/browse/MRESOLVER-373
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Blocker
> Fix For: 1.9.13
>
>
> The change done in MRESOLVER-346 in relation to DefaultArtifactResolver and
> DefaultMetadataResolver is wrong as it attempts lock upgrade. Also, is
> actually complemented by MRESOLVER-349 may not needed. The change happened
> for DefaultDeployer is correct.
> Problem is that now the pair (DefaultArtifactResolver and DefaultMetadata
> resolver) in case of model building involving snapshot parent POM attempt
> lock upgrade (unintentionally).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
