[
https://issues.apache.org/jira/browse/MRESOLVER-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17735278#comment-17735278
]
ASF GitHub Bot commented on MRESOLVER-373:
------------------------------------------
cstamas merged PR #303:
URL: https://github.com/apache/maven-resolver/pull/303
> 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)
