You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2006/08/30 15:09:48 UTC
[jira] Commented: (MNGECLIPSE-192) Exit code 1 - 'ssh' is not
recognized as an internal or external command,
[ http://jira.codehaus.org/browse/MNGECLIPSE-192?page=comments#action_73661 ]
Eugene Kuleshov commented on MNGECLIPSE-192:
--------------------------------------------
Please provide example project, configs and describe necessary configuration steps to reproduce this issue.
> Exit code 1 - 'ssh' is not recognized as an internal or external command,
> -------------------------------------------------------------------------
>
> Key: MNGECLIPSE-192
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-192
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Components: Maven Launcher
> Affects Versions: 0.0.9
> Environment: WIN XP SP2. Eclipse 3.2 Maven eclipse extension 0.0.9
> Reporter: Klingon Coder
> Assigned To: Eugene Kuleshov
>
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Dimensions Auto Build Application
> [INFO] task-segment: [deploy]
> [INFO] ----------------------------------------------------------------------------
> [INFO] plugin:descriptor
> [INFO] Using 2 extractors.
> [INFO] Applying extractor for language: java
> [INFO] Extractor for language: java found 2 mojo descriptors.
> [INFO] Applying extractor for language: bsh
> [INFO] Extractor for language: bsh found 0 mojo descriptors.
> [INFO] resources:resources
> [INFO] Using default encoding to copy filtered resources.
> [INFO] compiler:compile
> [INFO] Nothing to compile - all classes are up to date
> [INFO] resources:testResources
> [INFO] Using default encoding to copy filtered resources.
> [INFO] compiler:testCompile
> [INFO] No sources to compile
> [INFO] surefire:test
> [INFO] No tests to run.
> [INFO] jar:jar
> [INFO] Building jar: C:\workspace\dimensions-maven-plugin\target\dimensions-maven-plugin-1.0.jar
> [INFO] plugin:addPluginArtifactMetadata
> [INFO] install:install
> [INFO] Installing C:\workspace\dimensions-maven-plugin\target\dimensions-maven-plugin-1.0.jar to C:\Documents and Settings\user\.m2\repository\com\AutoBuild\dimensions-maven-plugin\1.0\dimensions-maven-plugin-1.0.jar
> [INFO] plugin:updateRegistry
> [INFO] deploy:deploy
> [ERROR] mojo-execute : deploy:deploy
> Diagnosis: Error deploying artifact: Error executing command for transfer
> FATAL ERROR: Error executing Maven for a project
> [ERROR] project-execute : com.AutoBuild:dimensions-maven-plugin:maven-plugin:1.0 ( task-segment: [deploy] )
> Diagnosis: Error deploying artifact: Error executing command for transfer
> FATAL ERROR: Error executing Maven for a project
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Error executing command for transfer
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:441)
> at org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:382)
> at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:68)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying artifact: Error executing command for transfer
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:145)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> ... 8 more
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Error executing command for transfer
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:133)
> ... 10 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Error executing command for transfer
> at org.apache.maven.wagon.providers.sshext.ScpExternalWagon.put(ScpExternalWagon.java:342)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
> ... 11 more
> Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code 1 - 'ssh' is not recognized as an internal or external command,
> operable program or batch file.
> at org.apache.maven.wagon.providers.sshext.ScpExternalWagon.executeCommand(ScpExternalWagon.java:217)
> at org.apache.maven.wagon.providers.sshext.ScpExternalWagon.executeCommand(ScpExternalWagon.java:378)
> at org.apache.maven.wagon.providers.sshext.ScpExternalWagon.put(ScpExternalWagon.java:338)
> ... 14 more
> I dont get this error while using command line version of maven (2.0.4). This issue seems to have been fixed in version 2.0.2 of maven. On command line the deploy to remote site works just fine.
--
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