[
http://jira.codehaus.org/browse/MRM-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96741
]
Joakim Erdfelt commented on MRM-212:
------------------------------------
Archiva trunk has a post-download policy for checksums.
Possible values for this policy.
* FAIL - if a bad checksum is downloaded, consider the downloaded file to be
bad, fail the attempt.
* FIX - if a bad checksum is downloaded, report it, and fix it, returning the
fixed checksum to the client.
* IGNORE - do not check the checksum.
> configure checksum policy for proxied repository
> ------------------------------------------------
>
> Key: MRM-212
> URL: http://jira.codehaus.org/browse/MRM-212
> Project: Archiva
> Issue Type: Improvement
> Components: remote proxy
> Reporter: nicolas de loof
> Priority: Critical
> Fix For: 0.9, 1.0
>
> Attachments: 2006-10-26-checksum-policy.patch, MRM-212.patch
>
>
> Some artifact on repo1.maven.org have bad checksum. This need fix, but this
> also make archiva not usable as a replacement for maven-proxy.
> As maven itself allow to configure a checksum policy, a new configuration
> parameter on proxied repo would be nice.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira