added a comment - - edited
As Lorenzo said :
We are having this problem with maven 2.2.1, wagon-webdav 1.0-beta-2, maven-site-plugin:2.1 on mvn site:deploy.
Reverting to maven-site-plugin:2.0 worked around the issue.
Same issue for me with maven 2.2.1 and maven-site-plugin:2.1.
Here is the context :
Multimodule project :
A : pom
B : jar
C : war
1) When I run mvn site from A, it doesn't work.
2) When I run mvn install from A, it works.
3) When I run mvn install site from A, it fails during the site phase for module C.
4) When I run mvn install site from C, it works.
It seems that the classpath for the first test includes commons-logging 1.0.4 (or 1.0.6) and commons-logging 1.1.1
For the second test, it uses only commons-logging 1.1.1
The third test add the two libs in classpath so it fails.
Is there a way to force maven to only use commons-logging 1.1.1 (for build, plugins, dependencies, ...) ?