Hi Wendy,
thanks for your suggestion. I am afraid, it didn't help: When declaring a
plugin dependency, the maven-site-plugin now has both
org.apache.maven.wagon:wagon-ssh-external:jar:1.0-beta-7 and
org.apache.maven.wagon:wagon-ssh:jar:1.0-beta-6 as a dependency, but it
still insists on using the latter for sftp URIs. :-(
Perhaps you need to exclude the one you don't want? Maven doesn't
recognize one as a replacement for the other, it just sees two
separate artifacts.
good point. Unfortunately, I don't see a way to do that. It looks like I
can only use <exclusions> to exclude *transitive* dependencies of a
plugin. At least the following plugin dependencies clause doesn't work:
<dependencies>
<dependency>
<exclusions>
<exclusion>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh</artifactId>
</exclusion>
</exclusions>
</dependency>
</dependencies>
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[ERROR]
'build.plugins.plugin[org.apache.maven.plugins:maven-site-plugin].dependencies.dependency.artifactId'
for null:null:jar is missing. @ line 151, column 27
[ERROR]
'build.plugins.plugin[org.apache.maven.plugins:maven-site-plugin].dependencies.dependency.groupId'
for null:null:jar is missing. @ line 151, column 27
[ERROR]
'build.plugins.plugin[org.apache.maven.plugins:maven-site-plugin].dependencies.dependency.version'
for null:null:jar is missing. @ line 151, column 27
I am afraid this is an incarantion of
<http://jira.codehaus.org/browse/MNG-2163>. :-( Or am I mistaken?
Best wishes,
Andreas Sewe
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
