[MNG-4301] Invalid checksums on deploy when using webdav without extension

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Incomplete
• Affects Version/s: 2.2.1
• Component/s: Deployment
• Environment: n/a
• Assignee: Unassigned
• Reporter: Kevin Shekleton
• Created: 14/Aug/09 07:35
• Updated: 06/Apr/15 01:53
• Resolved: 22/Jan/14 20:31

Description

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?

Issue Links

• depends upon: WAGON-277 HttpClient wagon (wagon-http) uploads all files twice when preemptive authentication is disabled
• is depended upon by: MNG-4742 Multi-threaded artifact resolver corrupts artifacts on download
• is duplicated by: MNG-4726 Maven generates incorrect MD5 and SHA1 on deply
• is related to: MNG-4235 [regression] Maven 2.2.0 produces invalid checksums during deployment to secured HTTP repo
• relates to: WAGON-304 Wrong checksum when deploy with wagon:httpclient provider