[
http://jira.codehaus.org/browse/MRM-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89640
]
Wendy Smoak commented on MRM-212:
---------------------------------
Archiva definitely needs this feature. Right now, it will not proxy the latest
release of maven-gpg-plugin due to a bad checksum.
We need to fix the bad checksums in central and make it stop happening-- is it
the deploy plugin causing the problem?
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-gpg-plugin
Version: 1.0-alpha-3
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-gpg-plugin:pom:1.0-alpha-3
from the specified remote repositories:
central (http://localhost:8080/archiva/repository/releases),
...
>From the log file:
INFO | jvm 1 | 2007/03/10 10:23:52 | 2007-03-10 10:23:52,526
[SocketListener0-2] WARN ProxyRequestHandler - The checksum
'e4525958537d3b438ede7acb73bd10ba' did not match the remote value:
D41D8CD98F00B204E9800998ECF8427E
INFO | jvm 1 | 2007/03/10 10:23:52 | 2007-03-10 10:23:52,526
[SocketListener0-2] WARN ProxyRequestHandler - Skipping repository
Central Repository: Checksum failures occurred while downloading
org/apache/maven/plugins/maven-gpg-plugin/1.0-alpha-3/maven-gpg-plugin-1.0-alpha-3.pom
> 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: 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
