Re: How to use wagon-ssh-external instead of wagon-ssh?
Hi Brett, I think in the Maven 3 version of the site plugin, you need to add the wagon as a dependency of the site plugin, instead of as an extension (which only applies to the core deployment components). 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. :-( Any other suggestions? Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
On Mon, May 2, 2011 at 6:11 AM, Andreas Sewe s...@st.informatik.tu-darmstadt.de wrote: 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. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
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 groupIdorg.apache.maven.wagon/groupId artifactIdwagon-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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
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: Well, there's always the Version 99 does not exist option... Could you maybe set a dependency to that jar, and set the scope to runtime? Don't know if that will help though. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
Hi Wayne, Well, there's always the Version 99 does not exist option... that's something I couldn't get past Maven 3. Also tried optionaltrue/optional and a system-scoped dependency with an invalid systemPath, but to no avail. Could you maybe set a dependency to that jar, and set the scope to runtime? Don't know if that will help though. No, it didn't. :-( Thanks for the suggestions, though. Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
On 02/05/2011, at 8:11 PM, Andreas Sewe wrote: Hi Brett, I think in the Maven 3 version of the site plugin, you need to add the wagon as a dependency of the site plugin, instead of as an extension (which only applies to the core deployment components). 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. :-( Any other suggestions? Apologies for not noticing that detail sooner. The external wagon doesn't have a handler for sftp - only scpexe. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to use wagon-ssh-external instead of wagon-ssh?
Hi, I am facing some problems deploying my project's site using sftp. For testing purposes I thus want to switch wagons, namely from org.apache.maven.wagon:wagon-ssh:1.0-beta-7 to org.apache.maven.wagon:wagon-ssh-external:1.0-beta-7. However, even adding the appropriate extension to my POM doesn't convince the maven-site-plugin:3.0-beta-4-SNAPSHOT to pick a different wagon for the sftp URI scheme. extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh-external/artifactId version1.0-beta-6/version /extension At least, I still get the same exception, which clearly says that I am using the JSch-based Wagon and not an external ssh process: Caused by: 3: Permission denied at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2291) at com.jcraft.jsch.ChannelSftp.mkdir(ChannelSftp.java:1701) at org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.mkdir(SftpWagon.java:204) at org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.mkdirs(SftpWagon.java:184) at org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.putDirectory(SftpWagon.java:271) ... 25 more [ERROR] Any suggestions? How does the maven-site-plugin map URI schemes to wagons? Also, is there any configuration option / system property to make the wagon more chatty? Just running mvn site-deploy -X doesn't produce enough information to track down what's actually going over the wire. :-( Best wishes, Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use wagon-ssh-external instead of wagon-ssh?
I think in the Maven 3 version of the site plugin, you need to add the wagon as a dependency of the site plugin, instead of as an extension (which only applies to the core deployment components). On 02/05/2011, at 1:05 AM, Andreas Sewe wrote: Hi, I am facing some problems deploying my project's site using sftp. For testing purposes I thus want to switch wagons, namely from org.apache.maven.wagon:wagon-ssh:1.0-beta-7 to org.apache.maven.wagon:wagon-ssh-external:1.0-beta-7. However, even adding the appropriate extension to my POM doesn't convince the maven-site-plugin:3.0-beta-4-SNAPSHOT to pick a different wagon for the sftp URI scheme. extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh-external/artifactId version1.0-beta-6/version /extension At least, I still get the same exception, which clearly says that I am using the JSch-based Wagon and not an external ssh process: Caused by: 3: Permission denied at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2291) at com.jcraft.jsch.ChannelSftp.mkdir(ChannelSftp.java:1701) at org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.mkdir(SftpWagon.java:204) at org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.mkdirs(SftpWagon.java:184) at org.apache.maven.wagon.providers.ssh.jsch.SftpWagon.putDirectory(SftpWagon.java:271) ... 25 more [ERROR] Any suggestions? How does the maven-site-plugin map URI schemes to wagons? Also, is there any configuration option / system property to make the wagon more chatty? Just running mvn site-deploy -X doesn't produce enough information to track down what's actually going over the wire. :-( Best wishes, Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
