[
https://jira.codehaus.org/browse/MSITE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290693#comment-290693
]
Anders Hammar commented on MSITE-629:
-------------------------------------
Yes, that works!
I was thinking of that solution, but at the time of writing this ticket I
didn't think that I should be forced to add it manually. But now I'm not that
sure any more. What I don't really understand is why it works without this
extra dep when the wagon is added as a global extension. There has to be a
slf4j impl somewhere on the classpath. Why isn't it available when the wagon is
added as a dep to the m-site-p?
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>
> Key: MSITE-629
> URL: https://jira.codehaus.org/browse/MSITE-629
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 3.0
> 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
