[
https://issues.apache.org/jira/browse/MRESOLVER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák resolved MRESOLVER-237.
---------------------------------------
Resolution: Fixed
> Make all checksum mismatches handled same
> -----------------------------------------
>
> Key: MRESOLVER-237
> URL: https://issues.apache.org/jira/browse/MRESOLVER-237
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamás Cservenák
> Assignee: Tamás Cservenák
> Priority: Major
> Fix For: 1.8.0
>
>
> Currently (1.7.x releases) the "included" (inlined) checksums produce "soft
> fail" and resolver goes for download of remote external checksum. In 1.8.x
> line where we added 3rd checksum kind (provided), all 3 of kinds should be
> treated equally.
> Also improve error message, it was: {{Checksum validation failed, expected
> BAD but is cf43b5391de623b36fe066a21127baef82c64022}} but make it tell more:
> {{Checksum validation failed, expected 'BAD' (PROVIDED) but is
> 'cf43b5391de623b36fe066a21127baef82c64022' (actual)}}
> (added single quotes around checksums and tell their origin)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
