[WAGON-370] Adding additional wagon provider as dependency does not work

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.3
• Component/s: wagon-webdav
• 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
• Assignee: Unassigned
• Reporter: Anders Hammar
• Created: 01/Feb/12 01:52
• Updated: 19/Nov/12 15:05
• Resolved: 19/Nov/12 15:05

Description

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.

Issue Links

• is related to: WAGON-329 FtpWagon currently tries to invoka an invalid MKD command with nested directories