[
https://issues.apache.org/jira/browse/MRESOLVER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246827#comment-17246827
]
Robert Scholte commented on MRESOLVER-151:
------------------------------------------
All methods of
https://github.com/apache/maven-resolver/blob/master/maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultChecksumPolicyProvider.java
provide a policy, but every unknown policy if automatically transformed to
some default. I still don't like that. If I apply a "super-strict" policy and
it doesn't exist, just throw an exception. It is not up to the
ChecksumPolicyProvider to just pick one (even with possible different outcome
based on the version of artifact-resolver)
It that doesn't work with MNG-5728, we need to revisit that issue.
> 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)
