You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Meeusen, Christopher W." <Me...@mayo.edu> on 2010/07/23 19:53:10 UTC
mvn site:deploy error
Hi,
I'm trying to transfer a directory of files to our web server, and I
thought that using mvn site:deploy would do what I want, but I'm getting
an error when I run the site:deploy command. I'm running from Windows 7
scp'ing to linux 10.04 server edition. The linux system has openSSH
already installed. I'm trying to follow the documentation here
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-
external.html, but I must be missing something.... I've already
downloaded the plink.exe file and added the directory to my path
variable.
Thanks!
Chris
Here is my pom.xml settings:
<distributionManagement>
<repository>
<id>r0210112</id>
<url>scpexe://var/www/wsaxis2M</url>
</repository>
</distributionManagement>
<build>
<extensions>
<!-- Enabling the use of FTP -->
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>1.0-beta-6</version>
</extension>
</extensions>
And my setup in my settings.xml
<server>
<id>r0210112</id>
<username>maven</username>
<password>PASSWORD</password>
<filePermissions>644</filePermissions>
<directoryPermissions>755</directoryPermissions>
<!-- <privateKey>/path/to/your/private/key</privateKey> not needed
if using pageant -->
<configuration>
<sshExecutable>plink</sshExecutable>
<scpExecutable>pscp</scpExecutable>
<!-- <sshArgs>other arguments you may need</sshArgs> -->
</configuration>
</server>
Error message:
ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy)
on project wsaxisM: Error deploying artifact: Error executing command
for transfer: Exit code 1 - 'ssh' is not recognized as an internal or
external command,
operable program or batch file.
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
(default-deploy) on project wsaxisM: Error deploying artifact: Error
executing command for transfer
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:585)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:324)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche
r.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2
30)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc
her.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352
)
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:195)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui
ldPluginManager.java:105)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:577)
... 14 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(Defaul
tArtifactDeployer.java:92)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
... 16 more
Caused by: org.apache.maven.wagon.TransferFailedException: Error
executing command for transfer
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpEx
ternalWagon.java:395)
at
org.apache.maven.repository.legacy.DefaultWagonManager.putRemoteFile(Def
aultWagonManager.java:498)
at
org.apache.maven.repository.legacy.DefaultWagonManager.putArtifact(Defau
ltWagonManager.java:450)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul
tArtifactDeployer.java:82)
... 17 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.ssh.external.ScpExternalWagon.executeCo
mmand(ScpExternalWagon.java:209)
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCo
mmand(ScpExternalWagon.java:149)
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpEx
ternalWagon.java:389)
... 20 more
[ERROR]
Re: mvn site:deploy error
Posted by Dennis Lundberg <de...@apache.org>.
On 2010-07-26 15:13, Meeusen, Christopher W. wrote:
> We have testNG reports generated under /${basedir}/test-output, and
> javadoc generated under /${basedir}/target/apidocs/ that I was trying
> to upload through SCP to our apache webserver using Maven. I thought
> that mvn site-deploy might do this, but I guess there is some
> incompatibilities with maven 3.0 and the maven-site-plugin.
I should be able to do that, but Maven 3 and the Site plugin currently
requires some extra configuration, see
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin
>
> I have since wrote some .bat files to handle the SCP, and will probably
> just use those to update our documentation.
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: users-return-112877-Meeusen.Christopher=mayo.edu@maven.apache.org
> [mailto:users-return-112877-Meeusen.Christopher=mayo.edu@maven.apache.or
> g] On Behalf Of Dennis Lundberg
> Sent: Saturday, July 24, 2010 4:13 PM
> To: Maven Users List
> Subject: Re: mvn site:deploy error
>
> What is it you are trying to achieve here?
>
> It doesn't seem to involve "site:deploy" like the subject says. What
> command are you running on the command line?
>
> On 2010-07-23 19:53, Meeusen, Christopher W. wrote:
>> Hi,
>>
>>
>>
>> I'm trying to transfer a directory of files to our web server, and I
>> thought that using mvn site:deploy would do what I want, but I'm
>> getting an error when I run the site:deploy command. I'm running from
>
>> Windows 7 scp'ing to linux 10.04 server edition. The linux system has
> openSSH
>> already installed. I'm trying to follow the documentation here
>> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ss
>> h- external.html, but I must be missing something.... I've already
>> downloaded the plink.exe file and added the directory to my path
>> variable.
>>
>>
>>
>>
>>
>> Thanks!
>>
>> Chris
>>
>>
>>
>> Here is my pom.xml settings:
>>
>>
>>
>> <distributionManagement>
>>
>> <repository>
>>
>> <id>r0210112</id>
>>
>> <url>scpexe://var/www/wsaxis2M</url>
>>
>> </repository>
>>
>> </distributionManagement>
>>
>>
>>
>> <build>
>>
>>
>>
>> <extensions>
>>
>> <!-- Enabling the use of FTP -->
>>
>> <extension>
>>
>> <groupId>org.apache.maven.wagon</groupId>
>>
>> <artifactId>wagon-ssh-external</artifactId>
>>
>> <version>1.0-beta-6</version>
>>
>> </extension>
>>
>> </extensions>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> And my setup in my settings.xml
>>
>> <server>
>>
>> <id>r0210112</id>
>>
>> <username>maven</username>
>>
>> <password>PASSWORD</password>
>>
>> <filePermissions>644</filePermissions>
>>
>> <directoryPermissions>755</directoryPermissions>
>>
>> <!-- <privateKey>/path/to/your/private/key</privateKey> not
>> needed if using pageant -->
>>
>> <configuration>
>>
>> <sshExecutable>plink</sshExecutable>
>>
>> <scpExecutable>pscp</scpExecutable>
>>
>> <!-- <sshArgs>other arguments you may need</sshArgs> -->
>>
>> </configuration>
>>
>> </server>
>>
>>
>>
>>
>>
>>
>>
>> Error message:
>>
>>
>>
>> ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
>> (default-deploy) on project wsaxisM: Error deploying artifact: Error
>> executing command for transfer: Exit code 1 - 'ssh' is not recognized
>> as an internal or external command,
>>
>> operable program or batch file.
>>
>> -> [Help 1]
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
>> (default-deploy) on project wsaxisM: Error deploying artifact: Error
>> executing command for transfer
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
>> ec
>> ycleExecutor.java:585)
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
>> ec
>> ycleExecutor.java:324)
>>
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
>>
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
>>
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
>>
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
>>
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
>> av
>> a:39)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
>> or
>> Impl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launc
>> he
>> r.java:290)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java
>> :2
>> 30)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Lau
>> nc
>> her.java:409)
>>
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:3
>> 52
>> )
>>
>> 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:195)
>>
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultB
>> ui
>> ldPluginManager.java:105)
>>
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
>> ec
>> ycleExecutor.java:577)
>>
>> ... 14 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(Defa
>> ul
>> tArtifactDeployer.java:92)
>>
>> at
>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
>>
>> ... 16 more
>>
>> Caused by: org.apache.maven.wagon.TransferFailedException: Error
>> executing command for transfer
>>
>> at
>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(Scp
>> Ex
>> ternalWagon.java:395)
>>
>> at
>> org.apache.maven.repository.legacy.DefaultWagonManager.putRemoteFile(D
>> ef
>> aultWagonManager.java:498)
>>
>> at
>> org.apache.maven.repository.legacy.DefaultWagonManager.putArtifact(Def
>> au
>> ltWagonManager.java:450)
>>
>> at
>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defa
>> ul
>> tArtifactDeployer.java:82)
>>
>> ... 17 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.ssh.external.ScpExternalWagon.execute
>> Co
>> mmand(ScpExternalWagon.java:209)
>>
>> at
>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.execute
>> Co
>> mmand(ScpExternalWagon.java:149)
>>
>> at
>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(Scp
>> Ex
>> ternalWagon.java:389)
>>
>> ... 20 more
>>
>> [ERROR]
>>
>>
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: mvn site:deploy error
Posted by "Meeusen, Christopher W." <Me...@mayo.edu>.
We have testNG reports generated under /${basedir}/test-output, and
javadoc generated under /${basedir}/target/apidocs/ that I was trying
to upload through SCP to our apache webserver using Maven. I thought
that mvn site-deploy might do this, but I guess there is some
incompatibilities with maven 3.0 and the maven-site-plugin.
I have since wrote some .bat files to handle the SCP, and will probably
just use those to update our documentation.
Thanks,
Chris
-----Original Message-----
From: users-return-112877-Meeusen.Christopher=mayo.edu@maven.apache.org
[mailto:users-return-112877-Meeusen.Christopher=mayo.edu@maven.apache.or
g] On Behalf Of Dennis Lundberg
Sent: Saturday, July 24, 2010 4:13 PM
To: Maven Users List
Subject: Re: mvn site:deploy error
What is it you are trying to achieve here?
It doesn't seem to involve "site:deploy" like the subject says. What
command are you running on the command line?
On 2010-07-23 19:53, Meeusen, Christopher W. wrote:
> Hi,
>
>
>
> I'm trying to transfer a directory of files to our web server, and I
> thought that using mvn site:deploy would do what I want, but I'm
> getting an error when I run the site:deploy command. I'm running from
> Windows 7 scp'ing to linux 10.04 server edition. The linux system has
openSSH
> already installed. I'm trying to follow the documentation here
> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ss
> h- external.html, but I must be missing something.... I've already
> downloaded the plink.exe file and added the directory to my path
> variable.
>
>
>
>
>
> Thanks!
>
> Chris
>
>
>
> Here is my pom.xml settings:
>
>
>
> <distributionManagement>
>
> <repository>
>
> <id>r0210112</id>
>
> <url>scpexe://var/www/wsaxis2M</url>
>
> </repository>
>
> </distributionManagement>
>
>
>
> <build>
>
>
>
> <extensions>
>
> <!-- Enabling the use of FTP -->
>
> <extension>
>
> <groupId>org.apache.maven.wagon</groupId>
>
> <artifactId>wagon-ssh-external</artifactId>
>
> <version>1.0-beta-6</version>
>
> </extension>
>
> </extensions>
>
>
>
>
>
>
>
>
>
> And my setup in my settings.xml
>
> <server>
>
> <id>r0210112</id>
>
> <username>maven</username>
>
> <password>PASSWORD</password>
>
> <filePermissions>644</filePermissions>
>
> <directoryPermissions>755</directoryPermissions>
>
> <!-- <privateKey>/path/to/your/private/key</privateKey> not
> needed if using pageant -->
>
> <configuration>
>
> <sshExecutable>plink</sshExecutable>
>
> <scpExecutable>pscp</scpExecutable>
>
> <!-- <sshArgs>other arguments you may need</sshArgs> -->
>
> </configuration>
>
> </server>
>
>
>
>
>
>
>
> Error message:
>
>
>
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
> (default-deploy) on project wsaxisM: Error deploying artifact: Error
> executing command for transfer: Exit code 1 - 'ssh' is not recognized
> as an internal or external command,
>
> operable program or batch file.
>
> -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
> (default-deploy) on project wsaxisM: Error deploying artifact: Error
> executing command for transfer
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> ec
> ycleExecutor.java:585)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> ec
> ycleExecutor.java:324)
>
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> av
> a:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launc
> he
> r.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java
> :2
> 30)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Lau
> nc
> her.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:3
> 52
> )
>
> 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:195)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultB
> ui
> ldPluginManager.java:105)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLif
> ec
> ycleExecutor.java:577)
>
> ... 14 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(Defa
> ul
> tArtifactDeployer.java:92)
>
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
>
> ... 16 more
>
> Caused by: org.apache.maven.wagon.TransferFailedException: Error
> executing command for transfer
>
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(Scp
> Ex
> ternalWagon.java:395)
>
> at
> org.apache.maven.repository.legacy.DefaultWagonManager.putRemoteFile(D
> ef
> aultWagonManager.java:498)
>
> at
> org.apache.maven.repository.legacy.DefaultWagonManager.putArtifact(Def
> au
> ltWagonManager.java:450)
>
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defa
> ul
> tArtifactDeployer.java:82)
>
> ... 17 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.ssh.external.ScpExternalWagon.execute
> Co
> mmand(ScpExternalWagon.java:209)
>
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.execute
> Co
> mmand(ScpExternalWagon.java:149)
>
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(Scp
> Ex
> ternalWagon.java:389)
>
> ... 20 more
>
> [ERROR]
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: mvn site:deploy error
Posted by Dennis Lundberg <de...@apache.org>.
What is it you are trying to achieve here?
It doesn't seem to involve "site:deploy" like the subject says. What
command are you running on the command line?
On 2010-07-23 19:53, Meeusen, Christopher W. wrote:
> Hi,
>
>
>
> I'm trying to transfer a directory of files to our web server, and I
> thought that using mvn site:deploy would do what I want, but I'm getting
> an error when I run the site:deploy command. I'm running from Windows 7
> scp'ing to linux 10.04 server edition. The linux system has openSSH
> already installed. I'm trying to follow the documentation here
> http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-
> external.html, but I must be missing something.... I've already
> downloaded the plink.exe file and added the directory to my path
> variable.
>
>
>
>
>
> Thanks!
>
> Chris
>
>
>
> Here is my pom.xml settings:
>
>
>
> <distributionManagement>
>
> <repository>
>
> <id>r0210112</id>
>
> <url>scpexe://var/www/wsaxis2M</url>
>
> </repository>
>
> </distributionManagement>
>
>
>
> <build>
>
>
>
> <extensions>
>
> <!-- Enabling the use of FTP -->
>
> <extension>
>
> <groupId>org.apache.maven.wagon</groupId>
>
> <artifactId>wagon-ssh-external</artifactId>
>
> <version>1.0-beta-6</version>
>
> </extension>
>
> </extensions>
>
>
>
>
>
>
>
>
>
> And my setup in my settings.xml
>
> <server>
>
> <id>r0210112</id>
>
> <username>maven</username>
>
> <password>PASSWORD</password>
>
> <filePermissions>644</filePermissions>
>
> <directoryPermissions>755</directoryPermissions>
>
> <!-- <privateKey>/path/to/your/private/key</privateKey> not needed
> if using pageant -->
>
> <configuration>
>
> <sshExecutable>plink</sshExecutable>
>
> <scpExecutable>pscp</scpExecutable>
>
> <!-- <sshArgs>other arguments you may need</sshArgs> -->
>
> </configuration>
>
> </server>
>
>
>
>
>
>
>
> Error message:
>
>
>
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy)
> on project wsaxisM: Error deploying artifact: Error executing command
> for transfer: Exit code 1 - 'ssh' is not recognized as an internal or
> external command,
>
> operable program or batch file.
>
> -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
> (default-deploy) on project wsaxisM: Error deploying artifact: Error
> executing command for transfer
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:585)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:324)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launche
> r.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:2
> 30)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launc
> her.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352
> )
>
> 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:195)
>
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBui
> ldPluginManager.java:105)
>
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:577)
>
> ... 14 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(Defaul
> tArtifactDeployer.java:92)
>
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
>
> ... 16 more
>
> Caused by: org.apache.maven.wagon.TransferFailedException: Error
> executing command for transfer
>
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpEx
> ternalWagon.java:395)
>
> at
> org.apache.maven.repository.legacy.DefaultWagonManager.putRemoteFile(Def
> aultWagonManager.java:498)
>
> at
> org.apache.maven.repository.legacy.DefaultWagonManager.putArtifact(Defau
> ltWagonManager.java:450)
>
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(Defaul
> tArtifactDeployer.java:82)
>
> ... 17 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.ssh.external.ScpExternalWagon.executeCo
> mmand(ScpExternalWagon.java:209)
>
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCo
> mmand(ScpExternalWagon.java:149)
>
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpEx
> ternalWagon.java:389)
>
> ... 20 more
>
> [ERROR]
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: mvn site:deploy error
Posted by "Meeusen, Christopher W." <Me...@mayo.edu>.
Well I'm on a windows 7 box, so AFAIK ssh isn't built into windows. You have to use a took like Plink or PSCP to get the maven-site-plugin to deploy to a webserver. I downloaded PLINK and and PSCP and pointed to their executables like so:
-----Original Message-----
From: users-return-112896-Meeusen.Christopher=mayo.edu@maven.apache.org [mailto:users-return-112896-Meeusen.Christopher=mayo.edu@maven.apache.org] On Behalf Of Wayne Fay
Sent: Monday, July 26, 2010 9:12 AM
To: Maven Users List
Subject: Re: mvn site:deploy error
> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
> (default-deploy) on project wsaxisM: Error deploying artifact: Error
> executing command for transfer: Exit code 1 - 'ssh' is not recognized
> as an internal or external command, operable program or batch file.
Hopefully you realized by now that this means m-deploy-p cannot find ssh installed on the box, right? Fix your path.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: mvn site:deploy error
Posted by "Meeusen, Christopher W." <Me...@mayo.edu>.
So hit send on accident...
Pointed to their exes like so:
<servers>
<server>
<id>r0210112</id>
<username>maven</username>
<password>j@v@d0c</password>
<filePermissions>644</filePermissions>
<directoryPermissions>755</directoryPermissions>
<configuration>
<sshExecutable>C:\putty\plink</sshExecutable>
<scpExecutable>C:\putty\pscp</scpExecutable>
</configuration>
</server>
This is the correct path, this is the exact same path im using in my .bats that are working...
Chris
-----Original Message-----
From: Meeusen, Christopher W.
Sent: Monday, July 26, 2010 9:17 AM
To: Maven Users List
Subject: RE: mvn site:deploy error
Well I'm on a windows 7 box, so AFAIK ssh isn't built into windows. You have to use a took like Plink or PSCP to get the maven-site-plugin to deploy to a webserver. I downloaded PLINK and and PSCP and pointed to their executables like so:
-----Original Message-----
From: users-return-112896-Meeusen.Christopher=mayo.edu@maven.apache.org [mailto:users-return-112896-Meeusen.Christopher=mayo.edu@maven.apache.org] On Behalf Of Wayne Fay
Sent: Monday, July 26, 2010 9:12 AM
To: Maven Users List
Subject: Re: mvn site:deploy error
> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy
> (default-deploy) on project wsaxisM: Error deploying artifact: Error
> executing command for transfer: Exit code 1 - 'ssh' is not recognized
> as an internal or external command, operable program or batch file.
Hopefully you realized by now that this means m-deploy-p cannot find ssh installed on the box, right? Fix your path.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: mvn site:deploy error
Posted by Wayne Fay <wa...@gmail.com>.
> org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy)
> on project wsaxisM: Error deploying artifact: Error executing command
> for transfer: Exit code 1 - 'ssh' is not recognized as an internal or
> external command, operable program or batch file.
Hopefully you realized by now that this means m-deploy-p cannot find
ssh installed on the box, right? Fix your path.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org