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

Posted to issues@maven.apache.org by "Tamás Cservenák (Jira)" <ji...@apache.org> on 2022/02/22 10:09:00 UTC

[jira] [Assigned] (MRESOLVER-241) Resolver checksum calculation should be driven by layout

     [ https://issues.apache.org/jira/browse/MRESOLVER-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamás Cservenák reassigned MRESOLVER-241:
-----------------------------------------

    Assignee: Tamás Cservenák

> Resolver checksum calculation should be driven by layout
> --------------------------------------------------------
>
>                 Key: MRESOLVER-241
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-241
>             Project: Maven Resolver
>          Issue Type: Bug
>          Components: Resolver
>            Reporter: Tamás Cservenák
>            Assignee: Tamás Cservenák
>            Priority: Major
>             Fix For: 1.8.0
>
>
> Currently, whether connector calculates checksums or not is driven by {{Layout.ChecksumLocation}}, but this is wrong, as some artifacts (like signatures) may not have checksum locations returned by layout, and hence, is shutting down complete checksum calculation. That, on the other hand, fails remote transport in case of FAIL checksum policy.
> This change alone does NOT fix special cases like "resolving from remote signature", but makes a step to fix it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)