maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <>
Subject [jira] Commented: (MNG-4301) Invalid checksums on deploy when using webdav without extension
Date Mon, 26 Jul 2010 20:50:32 GMT


Brian Fox commented on MNG-4301:

See the trick is that maven is producing these junk checksums upon upload. Even if you fix
it, until you repair the checksums in the repo, you will continue to get the checksum errors
whenever someone downloads those artifacts.

The workaround for this bug is to stop producing bad checksums, and then repair the ones that
are broken.

Stop producing bad checksums by: 
Not using Maven 2.2.0
or not using a wagon with httpclient against an authenticated repo unless you disable preemptive

If you're using Nexus, it can repair the checksums simply by doing a "Rebuild Maven Metadata"
on the subfolder of the repo where your busted checksums are.

> Invalid checksums on deploy when using webdav without extension
> ---------------------------------------------------------------
>                 Key: MNG-4301
>                 URL:
>             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
> <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:
For more information on JIRA, see:


View raw message