[ 
https://jira.codehaus.org/browse/WAGON-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dennis Lundberg moved MSITE-629 to WAGON-370:
---------------------------------------------

          Component/s:     (was: site:deploy)
                       wagon-webdav
    Affects Version/s:     (was: 3.0)
                       2.2
                  Key: WAGON-370  (was: MSITE-629)
              Project: Maven Wagon  (was: Maven 2.x and 3.x Site Plugin)
    
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
>                 Key: WAGON-370
>                 URL: https://jira.codehaus.org/browse/WAGON-370
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-webdav
>    Affects Versions: 2.2
>         Environment: Mac OS 10.7.2, Apple Java 1.6.0_29, Maven 3.0.3/3.0.4
> Windows XP, SUN Java 1.6.0_24, Maven 3.0.4
>            Reporter: Anders Hammar
>         Attachments: console.txt, mvnsite-dav-dep-bug.zip
>
>
> According to 
> http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html
>  is should be possible to add additional wagon provider as a dependency to 
> the site plugin. For a project deploying via dav, doing so using the 
> wagon-webdav-jackrabbit makes Maven through a NoClassDefFoundError. Of adding 
> the wagon as a global extension it works.
> Not sure if this is a maven-site-plugin issue though, or possible something 
> in the specific wagon.
> I'm attaching a test project as well as the console output showing the error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to