[
https://issues.apache.org/jira/browse/MRESOLVER-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506906#comment-17506906
]
Hudson commented on MRESOLVER-241:
----------------------------------
Build unstable in Jenkins: Maven » Maven TLP » maven-resolver » master #12
See
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/12/
> 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.
> The fact that {{Layout.ChecksumLocation}} is empty does not mean anything
> else, that resolver should not expect on remote checksum (REMOTE_EXTERNAL),
> but not shut down completely checksum validation as other mechanisms
> (REMOTE_INCLUDED or PROVIDED) should still kick in, if applicable.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
