[jira] Commented: (MNG-4301) Invalid checksums on deploy when using webdav without extension

["Stephen Pack (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195024#action_195024 ] 

Stephen Pack commented on MNG-4301:
-----------------------------------

I believe the previous comment is the workaround for maven 2.2.0; for maven 2.2.1, you need to add  <wagonProvider>httpclient</wagonProvider> in the configuration.  Without that addition, I got the exception "Cannot find setter nor field in org.apache.maven.wagon.providers.http.LightweightHttpWagon for 'httpConfiguration'"

> Invalid checksums on deploy when using webdav without extension
> ---------------------------------------------------------------
>
>                 Key: MNG-4301
>                 URL: http://jira.codehaus.org/browse/MNG-4301
>             Project: Maven 2
>          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