[
https://issues.apache.org/jira/browse/MRESOLVER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248055#comment-17248055
]
Michael Osipov commented on MRESOLVER-151:
------------------------------------------
OK, I have just checked both code bases. What Maven basically does is to create
a {{RepositoryPolicy}} with {{checksums}} {{fail}}. This value in turn is used
in Resolver to query the provider for a proper {{ChecksumProvider}}. So there
is no need to provide another provider. The defaults of Resolver only work when
the caller never provides a checksum policy. So consider you are using Resolver
in your custom code outside Maven land and create a repo with a default policy
right now you will get warnings only. You have to configure failures
explicitly. With this change your custom code will have failures immediately
during transports.
Is that clear? I expect sane callers to have fail enabled by explicitly.
> Switch the default checksum policy from "warn" to "fail"
> --------------------------------------------------------
>
> Key: MRESOLVER-151
> URL: https://issues.apache.org/jira/browse/MRESOLVER-151
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Affects Versions: 1.6.1
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 1.7.0
>
>
> This mirrors MNG-5728. The change has to happen in
> {{DefaultChecksumPolicyProvider}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
