[
https://issues.apache.org/jira/browse/MRESOLVER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248147#comment-17248147
]
Robert Scholte commented on MRESOLVER-151:
------------------------------------------
I think it is clear to me. So for Maven there's no need to change this, because
it provides an explicit policy.
For other tools that don't provide an explicit policy (or a non-existing
policy) it will now fall back to warn.
If we implement this change, if will fail instead.
As said I don't like the idea that Artifact Resolver decides the policy, that
should be up to the tool using it.
Ant tasks can say: my default is warn, unless I'm onfigured to use a different
policy,
With that: the IAE is still an option, right?
> 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)
