You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/04 08:44:06 UTC
[jira] Updated: (MNG-1358) scp:// urls not recognised, even when wagon-ssh is installed.
[ http://jira.codehaus.org/browse/MNG-1358?page=all ]
Brett Porter updated MNG-1358:
------------------------------
Description:
I have got the <install> task working to pull in the various deployment wagons
<target name="m2-wagons" depends="m2-pom,ssh-init">
<m2:install-provider artifactId="wagon-ssh"
version="${wagon-ssh.version}"/>
<m2:install-provider artifactId="wagon-ssh-external"
version="${wagon-ssh-external.version}"/>
<m2:install-provider artifactId="wagon-file"
version="${wagon-file.version}"/>
<m2:install-provider artifactId="wagon-ftp"
version="${wagon-ftp.version}"/>
</target>
But when I run a deploy target and use the scp:// protocol , I get the unknown protocol error.
<target name="m2-ssh-deploy" depends="m2-pom,ssh-init,m2-wagons">
<property name="m2.upload.url"
value="scp://${ssh.host}/www/repository"/>
<m2:deploy file="${target.jar}">
<remoteRepository url="${m2.upload.url}">
<authentication username="${ssh.user}"
privateKey="${ssh.keyfile}"/>
</remoteRepository>
<pom refid="m2.pom"/>
</m2:deploy>
</target>
This is only for scp:, the others, scpexe, file: and ftp: do work. Is the url schema wrong? Is there any way to enum what protocols are currently supported?
I would recommend that the error message "unsupported protocol" is supplemented with a listing of what protocols are supported. That way its easier to differentiate spelling error from uninstalled wagon.
was:
I have got the <install> task working to pull in the various deployment wagons
<target name="m2-wagons" depends="m2-pom,ssh-init">
<m2:install-provider artifactId="wagon-ssh"
version="${wagon-ssh.version}"/>
<m2:install-provider artifactId="wagon-ssh-external"
version="${wagon-ssh-external.version}"/>
<m2:install-provider artifactId="wagon-file"
version="${wagon-file.version}"/>
<m2:install-provider artifactId="wagon-ftp"
version="${wagon-ftp.version}"/>
</target>
But when I run a deploy target and use the scp:// protocol , I get the unknown protocol error.
<target name="m2-ssh-deploy" depends="m2-pom,ssh-init,m2-wagons">
<property name="m2.upload.url"
value="scp://${ssh.host}/www/repository"/>
<m2:deploy file="${target.jar}">
<remoteRepository url="${m2.upload.url}">
<authentication username="${ssh.user}"
privateKey="${ssh.keyfile}"/>
</remoteRepository>
<pom refid="m2.pom"/>
</m2:deploy>
</target>
This is only for scp:, the others, scpexe, file: and ftp: do work. Is the url schema wrong? Is there any way to enum what protocols are currently supported?
I would recommend that the error message "unsupported protocol" is supplemented with a listing of what protocols are supported. That way its easier to differentiate spelling error from uninstalled wagon.
Fix Version: 2.0.1
Environment:
can't see the error, but will make the error reporting improvements. It does work in the sample script.
> scp:// urls not recognised, even when wagon-ssh is installed.
> -------------------------------------------------------------
>
> Key: MNG-1358
> URL: http://jira.codehaus.org/browse/MNG-1358
> Project: Maven 2
> Type: Bug
> Components: maven-artifact-ant
> Versions: 2.0
> Reporter: Steve Loughran
> Priority: Minor
> Fix For: 2.0.1
>
>
> I have got the <install> task working to pull in the various deployment wagons
> <target name="m2-wagons" depends="m2-pom,ssh-init">
> <m2:install-provider artifactId="wagon-ssh"
> version="${wagon-ssh.version}"/>
> <m2:install-provider artifactId="wagon-ssh-external"
> version="${wagon-ssh-external.version}"/>
> <m2:install-provider artifactId="wagon-file"
> version="${wagon-file.version}"/>
> <m2:install-provider artifactId="wagon-ftp"
> version="${wagon-ftp.version}"/>
> </target>
> But when I run a deploy target and use the scp:// protocol , I get the unknown protocol error.
> <target name="m2-ssh-deploy" depends="m2-pom,ssh-init,m2-wagons">
>
> <property name="m2.upload.url"
> value="scp://${ssh.host}/www/repository"/>
> <m2:deploy file="${target.jar}">
> <remoteRepository url="${m2.upload.url}">
> <authentication username="${ssh.user}"
> privateKey="${ssh.keyfile}"/>
> </remoteRepository>
> <pom refid="m2.pom"/>
> </m2:deploy>
> </target>
> This is only for scp:, the others, scpexe, file: and ftp: do work. Is the url schema wrong? Is there any way to enum what protocols are currently supported?
> I would recommend that the error message "unsupported protocol" is supplemented with a listing of what protocols are supported. That way its easier to differentiate spelling error from uninstalled wagon.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org