[
https://jira.codehaus.org/browse/MNG-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332026#comment-332026
]
Marcin Wisnicki commented on MNG-339:
-------------------------------------
This was never fixed (or at least there is nothing in documentation on how to
globally set checksumPolicy and retry policy).
Also, since 8 years passed maybe it's a good time to rethink default behavior.
> improve checksum handling
> -------------------------
>
> Key: MNG-339
> URL: https://jira.codehaus.org/browse/MNG-339
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Brett Porter
> Assignee: John Casey
> Fix For: 2.0-alpha-3
>
>
> presently, missing or invalid checksums are just warned on. sha1 and md5 are
> always uploaded.
> - Need to pick one or the other for a repository (might choose to upload
> both, though probably not worth testing both on the way down)
> - Need a way to specify a master override (command line) to turn off strict
> checking of things like this and anything else (eg skip bad transitive deps)
> **
> - Might want to retry on failure?
> ** had a discussion about this and it seems better to do this than to
> allow it to be specified in the project, to encourage those that have bad
> metadata to fix it. Need to still reassess the impact on the user, but we are
> in a position to make sure repo1 is verified and its integrity is maintained.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
