This is probably because you need a passphrase or agent to connect using that key. Unfortunately this is not supported by Jsch yet.
You can use an external scp app by using the scpexe:// protocol. - Brett On 8/5/05, andrew <[EMAIL PROTECTED]> wrote: > Maven version: 2.0-beta-1-SNAPSHOT, and > Maven version: 2.0-alpha-3 > > Hi, > > I am attempting to deploy to our repository server via scp. > > In ~/.m2/settings.xml I have: > > <servers> > <server> > <id>repos</id> > <username>amm</username> > <privateKey>/home/amm/.ssh/id_dsa</privateKey> > </server> > </servers> > > and in pom.xml: > > <distributionManagement> > <repository> > <id>repos</id> > <url>scp://server/path/to/deploy/repos</url> > </repository> > </distributionManagement> > > From a command line I can: > > $ scp foo.xml server:/path/to/deploy/repos, OR > $ scp foo.xml [EMAIL PROTECTED]:/path/to/deploy/repos > > without any trouble. I am caching my key's password with ssh-agent. > > When I attempt to deploy I receive the following exceptions: > > $ m2 deploy:deploy > [INFO] Using local copy of plugins.xml (plugin mappings) for group: > 'org.apache.maven.plugins' from: > /home/amm/.m2/repository/org/apache/maven/plugins/plugins.xml > [INFO] maven-deploy-plugin: resolved to version 2.0-alpha-3 from local > repository > [INFO] > ---------------------------------------------------------------------------- > [INFO] Building Distra > [INFO] task-segment: [deploy:deploy] > [INFO] > ---------------------------------------------------------------------------- > [INFO] [deploy:deploy] > [INFO] > ---------------------------------------------------------------------------- > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] Diagnosis: Error deploying artifact > [INFO] > ---------------------------------------------------------------------------- > [ERROR] Cause: > org.apache.maven.plugin.MojoExecutionException: Error deploying artifact > at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:184) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:361) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:472) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:453) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:435) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:127) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:292) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:324) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: > org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error > deploying artifact: > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:49) > at > org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:172) > ... 16 more > Caused by: org.apache.maven.wagon.TransferFailedException: > Authentication failed: > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:185) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:92) > at > org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:72) > ... 18 more > Caused by: > org.apache.maven.wagon.authentication.AuthenticationException: Cannot > connect. Reason: Auth cancel > at > org.apache.maven.wagon.providers.ssh.ScpWagon.openConnection(ScpWagon.java:164) > at > org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java:123) > at > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:151) > ... 20 more > Caused by: com.jcraft.jsch.JSchException: Auth cancel > at com.jcraft.jsch.Session.connect(Unknown Source) > at com.jcraft.jsch.Session.connect(Unknown Source) > at > org.apache.maven.wagon.providers.ssh.ScpWagon.openConnection(ScpWagon.java:158) > ... 22 more > [INFO] > ---------------------------------------------------------------------------- > [INFO] Total time: < 1 second > [INFO] Finished at: Fri Aug 05 16:56:13 EST 2005 > [INFO] Final Memory: 1M/3M > [INFO] > ---------------------------------------------------------------------------- > > ScpWagon appears to be harvesting my username and key correctly (I get a > different exception if these are not specified in settings.xml) but > jsch.Session is barfing on the authentication. > > Any ideas? > > Is there any reason I need to have my username and key specified in > settings.xml at all? Couldn't m2 just delegate to ssh (as for command > line scp) by default? > > Thanks, > ...andrew > -- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
