maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <>
Subject [jira] (MSITE-629) Adding additional wagon provider as dependency does not work
Date Fri, 03 Feb 2012 23:24:03 GMT


Dennis Lundberg commented on MSITE-629:

I think wagon needs to have some dependency on slf4j. When I looked at svn history for the
POM there was a commit that removed such a dependency. I'll go and add that back. Until then
you can use the above as a temporary workaround.
> Adding additional wagon provider as dependency does not work
> ------------------------------------------------------------
>                 Key: MSITE-629
>                 URL:
>             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,
> According to
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
> 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:!default.jspa
For more information on JIRA, see:


View raw message