[ http://jira.codehaus.org/browse/MRM-212?page=comments#action_78739 ] Henri Yandell commented on MRM-212: -----------------------------------
Seems like a good start to me Raphael, and it doesn't seem to break anything. I'm not sure on the direction though - seems to me that after running the report I would want to then say "Now fix things", rather than have anything happen automatically. I'm not sure if automatic is the direction you're going. (I'm new to Archiva though, so not sure what the planned direction is on many things) > configure checksum policty 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: Minor > Attachments: 2006-10-26-checksum-policy.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
