[
http://jira.codehaus.org/browse/MNG-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229854#action_229854
]
Cornel Masson commented on MNG-4301:
------------------------------------
We are experiencing the same bug and it's now a show-stopper for our Maven
release. We have a large build and are seeing numerous CHECKSUM failures, even
on Maven jars from Central.
We are using:
* Maven 2.2.1
* Nexus Open Source Edition, Version: 1.6.0
We have tried all the suggestions on the Net, including:
* setting the wagon provider to httpclient
* setting http.authentication.preemptive to true (as above)
* setting the specific wagon-webdav version (as above)
and nothing works. Each time we run the build, a random selection of artifacts
fail with CHECKSUM errors. This happens for both internal (self-deployed) and
external artifacts.
Here's an example failure:
4425K downloaded (groovy-all-1.6.5.jar)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'9c6a38100085d8fbfb3f017ac82e396999e64f92'; remote = 'PK
If you examine the remote checksum, it seems it references the actual
*contents* of the JAR, not a checksum file(!!).
We also get 'invalid POM' errors as a result of some failures, so our build
actually breaks at the end (no use just ignoring the bad checksums). Example:
40b downloaded (plexus-utils-1.5.6.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'8394a409e7b98020aac9429157265db0fb8cfac6'; remote = '<?xml' - IGNORING
[WARNING] POM for 'org.codehaus.plexus:plexus-utils:pom:1.5.6:runtime' is
invalid.
Please help!
> Invalid checksums on deploy when using webdav without extension
> ---------------------------------------------------------------
>
> Key: MNG-4301
> URL: http://jira.codehaus.org/browse/MNG-4301
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 2.2.1
> Environment: n/a
> Reporter: Kevin Shekleton
> Priority: Blocker
>
> With maven 2.2.1, our deployments via webdav are producing invalid checksums,
> similar to the issue reported in MNG-4235.
> From maven 2.0.8 and previous, the following build extension was required to
> deploy via webdav:
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-webdav</artifactId>
> <version>1.0-beta-2</version>
> </extension>
> </extensions>
> Starting with maven 2.0.9 (see MNG-3418), webdav was included by default and
> the aforementioned build extension must be removed from the project. If it
> was included in the project the deployment would fail as Maven would report
> multiple versions of wagon-webdav present.
> With maven 2.2.0, our deployment suffered from invalid checksums reported in
> MNG-4235.
> With maven 2.2.1, we still see the invalid checksums on deployment as
> reported in MNG-4235. However, I've found that if you add the above build
> extension into the project, we don't experience this issue (of generating
> invalid checksums). Is this workaround an intentional change brought about
> by the fix of MNG-4235?
--
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
