You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mick Knutson <mi...@gmail.com> on 2007/11/08 00:38:40 UTC
[ms] issues with ssh connection to repo?
I want to connect to a remote repository with a different user than I am
when I am compiling:
<server>
<id>remote-esp-dap-site</id>
<username>maven_user</username>
<passphrase>somephrase</passphrase>
<privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
<configuration>
<sshExecutable>plink</sshExecutable>
<scpExecutable>pscp</scpExecutable>
</configuration>
</server>
<distributionManagement>
<site>
<id>rc_sun66e</id>
<name>DAP-Site</name>
<url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
</site>
</distributionManagement>
But I get this error:
[INFO] [site:deploy]
scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities - Session:
Opened
Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
Settings\dnxmkk5\.ssh\id_rsa"
-o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
opt/htdocs/site/utilities/."'
'ssh' is not recognized as an internal or external command,
operable program or batch file.
scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities - Session:
Disconnecting
scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities - Session:
Disconnected
I want to use the maven_user not dnxmkk5 user. But there also seems to be an
issue with the command that is generated.
I tried following these directions:
http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remote.html
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Re: [ms] issues with ssh connection to repo?
Posted by Mick Knutson <mi...@gmail.com>.
Thanks! Works great!
On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
>
> You need to use the same id in your distribution management section in
> your pom, as the server settings you want to use from server.xml. In
> your case that would be 'remote-esp-dap-site'.
>
> So putting this in your pom.xml should do it:
>
> <distributionManagement>
> <site>
> <id>remote-esp-dap-site</id>
> <name>DAP-Site</name>
>
> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> </site>
> </distributionManagement>
>
>
> Mick Knutson wrote:
> > I want to connect to a remote repository with a different user than I am
> > when I am compiling:
> >
> > <server>
> > <id>remote-esp-dap-site</id>
> > <username>maven_user</username>
> > <passphrase>somephrase</passphrase>
> > <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> > <configuration>
> > <sshExecutable>plink</sshExecutable>
> > <scpExecutable>pscp</scpExecutable>
> > </configuration>
> > </server>
> >
> >
> > <distributionManagement>
> > <site>
> > <id>rc_sun66e</id>
> > <name>DAP-Site</name>
> > <url>scpexe://rc-sun66e.ut.dentegra.lab
> /:/opt/htdocs/site/</url>
> > </site>
> > </distributionManagement>
> >
> >
> > But I get this error:
> >
> > [INFO] [site:deploy]
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Opened
> > Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> > Settings\dnxmkk5\.ssh\id_rsa"
> > -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> > opt/htdocs/site/utilities/."'
> >
> > 'ssh' is not recognized as an internal or external command,
> > operable program or batch file.
> >
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Disconnecting
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Disconnected
> >
> >
> >
> > I want to use the maven_user not dnxmkk5 user. But there also seems to
> be an
> > issue with the command that is generated.
> >
> > I tried following these directions:
> >
> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remote.html
> >
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Re: [ms] issues with ssh connection to repo?
Posted by Mick Knutson <mi...@gmail.com>.
Thanks very much for all your help!
On 11/8/07, Dennis Lundberg <de...@apache.org> wrote:
>
> I'm not sure. I experimented with the different executables in the putty
> distribution once, and still have that config in my settings.xml, but
> it's commented out. I haven't had the need to use it in production since
> the servers I deploy to works happily using scp:
>
> Mick Knutson wrote:
> > Awesome. So should I use plink for site & repo? as it putty seemed to
> work
> > for the site already.
> >
> >
> > On 11/8/07, Dennis Lundberg <de...@apache.org> wrote:
> >> Just a tip to help debug this: use different id:s for the site and the
> >> repository. Here at Apache we uses the id:s "apache.site" and
> >> "apache.releases" respectively. That way the configurations are sure to
> >> not intertwine with each other.
> >>
> >> I think you should use plink instead of putty for your <sshExecutable>
> >>
> >> Mick Knutson wrote:
> >>> :-O this is crazy.
> >>>
> >>> so for site 'scp:' works, but for the repo, I need to use
> 'scpexe:'....
> >>>
> >>> Ok, I did that, then putty opened and alert dialog saying "invalid
> >> option
> >>> -o"
> >>> I clicked Ok, then there was this error:
> >>>
> >>> [INFO] [deploy:deploy]
> >>> altDeploymentRepository = null
> >>> [INFO] Retrieving previous build number from rc_sun66e
> >>> Uploading: scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
> >>> /org/delta/esp/dap/E1B-1.0-SNAPSHOT/dap-E1B-1.0-20071108.191732-1.pom
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [ERROR] BUILD ERROR
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] Error deploying artifact: Error executing command for transfer
> >>>
> >>> Exit code 1 -
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] Trace
> >>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> deploying
> >>> artifact: Error executing command for transfer
> >>> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> >>> DefaultLifecycleExecutor.java:564)
> >>> at
> >>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> >>> (DefaultLifecycleExecutor.java:480)
> >>> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> >>> DefaultLifecycleExecutor.java:459)
> >>> at
> >>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> >>> (DefaultLifecycleExecutor.java:311)
> >>> at
> >>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> >>> DefaultLifecycleExecutor.java:278)
> >>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> (
> >>> DefaultLifecycleExecutor.java:143)
> >>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
> >> :334)
> >>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java
> :125)
> >>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> >>> 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:585)
> >>> 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.plugin.MojoExecutionException: Error
> >> deploying
> >>> artifact: Error executing command for transfer
> >>> at org.apache.maven.plugin.deploy.DeployMojo.execute(
> >> DeployMojo.java
> >>> :174)
> >>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> >>> DefaultPluginManager.java:443)
> >>> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> >>> DefaultLifecycleExecutor.java:539)
> >>> ... 16 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:94)
> >>> at org.apache.maven.plugin.deploy.DeployMojo.execute(
> >> DeployMojo.java
> >>> :152)
> >>> ... 18 more
> >>> Caused by: org.apache.maven.wagon.TransferFailedException: Error
> >> executing
> >>> command for transfer
> >>> at
> >>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
> >>> ScpExternalWagon.java:290)
> >>> at
> >>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
> >>> DefaultWagonManager.java:237)
> >>> at
> >> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
> >>> (DefaultWagonManager.java:153)
> >>> at
> >> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> >>> (DefaultArtifactDeployer.java:80)
> >>> ... 19 more
> >>> Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code
> 1
> >> -
> >>> at
> >>>
> >>
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
> >>> (ScpExternalWagon.java:145)
> >>> at
> >>>
> >>
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
> >>> (ScpExternalWagon.java:326)
> >>> at
> >>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
> >>> ScpExternalWagon.java:286)
> >>>
> >>>
> >>>
> >>> I got the above error when I tried this URL formats:
> >>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
> >>> or
> >>> scpexe://rc-sun66e.ut.dentegra.lab/opt/htdocs/repository
> >>>
> >>>
> >>>
> >>>
> >>> On 11/8/07, Blue.Thomas@ubs.com <Bl...@ubs.com> wrote:
> >>>> You had it right before; Replace
> >>>> <url>scp:.. With
> >>>> <url>scpexe:..
> >>>>
> >>>> under <distributionManagement>
> >>>>
> >>>> -----Original Message-----
> >>>> From: Mick Knutson [mailto:mickknutson@gmail.com]
> >>>> Sent: Thursday, November 08, 2007 1:54 PM
> >>>> To: Maven Users List
> >>>> Subject: Re: [ms] issues with ssh connection to repo?
> >>>>
> >>>> I spoke too soon.
> >>>> I have the 'mvn site-deploy' working with the following server:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> <server>
> >>>> <id>rc_sun66e</id>
> >>>> <username>[username]</username>
> >>>> <password>[password]</password>
> >>>> <passphrase>[phrase]</passphrase>
> >>>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> >>>> <configuration>
> >>>> <sshExecutable>putty</sshExecutable> <!-- also tried
> >>>> plink
> >>>> -->
> >>>> <scpExecutable>pscp</scpExecutable>
> >>>> </configuration>
> >>>> </server>
> >>>>
> >>>> Then I have this:
> >>>>
> >>>> <distributionManagement>
> >>>> <site>
> >>>> <id>rc_sun66e</id>
> >>>> <name>DAP-Site</name>
> >>>> <url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
> >>>> project.version}</url>
> >>>> </site>
> >>>>
> >>>> <!-- use the following if you're not using a snapshot
> version.
> >>>> -->
> >>>> <repository>
> >>>> <id>rc_sun66e</id>
> >>>> <name>DAP-Repository</name>
> >>>> <url>scp://rc-sun66e.ut.dentegra.lab
> >>>> /:/opt/htdocs/repository</url>
> >>>> </repository>
> >>>> </distributionManagement>
> >>>>
> >>>>
> >>>> So if the site works fine, why do I get this with 'mvn clean deploy
> >> -e':
> >>>> [INFO] [deploy:deploy]
> >>>> altDeploymentRepository = null
> >>>> [INFO] Retrieving previous build number from rc_sun66e [WARNING]
> >>>> repository metadata for: 'snapshot org.delta.esp:dap:E1B-1.0-SNAPSHOT
> '
> >>>> could not be retrieved from repository:
> >>>> rc_sun66e due to an error: While c
> >>>> onfiguring wagon for 'rc_sun66e': Unable to apply wagon
> configuration.
> >>>> [INFO] Repository 'rc_sun66e' will be blacklisted [INFO]
> >>>>
> >>
> ------------------------------------------------------------------------
> >>>> [ERROR] BUILD ERROR
> >>>> [INFO]
> >>>>
> >>
> ------------------------------------------------------------------------
> >>>> [INFO] Error deploying artifact: While configuring wagon for
> >>>> 'rc_sun66e':
> >>>> Unable to apply wagon configuration.
> >>>>
> >>>> Cannot find setter nor field in
> >>>> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for
> 'sshExecutable'
> >>>> [INFO]
> >>>>
> >>
> ------------------------------------------------------------------------
> >>>> [INFO] Trace
> >>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> deploying
> >>>> artifact: While configuring wagon for 'rc_sun66e': Unable to apply
> >> wagon
> >>>> configuration.
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> >>>> DefaultLifecycleExecutor.java:564)
> >>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> >>>> ycle
> >>>> (DefaultLifecycleExecutor.java:480)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> >>>> DefaultLifecycleExecutor.java:459)
> >>>> at
> >>>>
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> >>>> Failures
> >>>> (DefaultLifecycleExecutor.java:311)
> >>>> at
> >>>>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
> >> (
> >>>> DefaultLifecycleExecutor.java:278)
> >>>> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> >>>> DefaultLifecycleExecutor.java:143)
> >>>> at
> >>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> >>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java
> :125)
> >>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> >>>> 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:585)
> >>>> 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.plugin.MojoExecutionException: Error
> >>>> deploying
> >>>> artifact: While configuring wagon for 'rc_sun66e': Unable to apply
> >> wagon
> >>>> configu ration.
> >>>> at
> >>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> >>>> :174)
> >>>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> >>>> DefaultPluginManager.java:443)
> >>>> at
> >>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> >>>> DefaultLifecycleExecutor.java:539)
> >>>> ... 16 more
> >>>> Caused by:
> >>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> >>>> Error deploying artifact: While configuring wagon for 'rc_sun66e':
> >>>> Unable to app ly wagon configuration.
> >>>> at
> >>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> >>>> (DefaultArtifactDeployer.java:94)
> >>>> at
> >>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> >>>> :152)
> >>>> ... 18 more
> >>>> Caused by:
> >>>> org.apache.maven.artifact.manager.WagonConfigurationException:
> >>>> While configuring wagon for 'rc_sun66e': Unable to apply wagon
> >>>> configuration.
> >>>> at
> >>>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> >>>> DefaultWagonManager.java:872)
> >>>> at
> >>>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> >>>> DefaultWagonManager.java:848)
> >>>> at
> >>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
> >>>> DefaultWagonManager.java:180)
> >>>> at
> >>>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
> >>>> (DefaultWagonManager.java:153)
> >>>> at
> >>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> >>>> (DefaultArtifactDeployer.java:80)
> >>>> ... 19 more
> >>>> Caused by:
> >>>>
> >>
> org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
> >>>> on:
> >>>> Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
> >>>> .jsch.ScpWagon for 'sshExecutable'
> >>>> at
> >>>>
> >>
> org.codehaus.plexus.component.configurator.converters.ComponentValueSett
> >>>> er
> >>>> .<init>(ComponentValueSetter.java:68)
> >>>> at
> >>>>
> >>
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
> >>>> thFieldsConverter.processConfiguration
> >>>> (ObjectWithFieldsConverter.java:13
> >>>> 4)
> >>>> at
> >>>>
> >>
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
> >>>> nfigureComponent
> >>>> (BasicComponentConfigurator.java:56)
> >>>> at
> >>>>
> >>
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
> >>>> .configureComponent
> >>>> (AbstractComponentConfigurator.java:54)
> >>>> at
> >>>>
> >>
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
> >>>> .configureComponent
> >>>> (AbstractComponentConfigurator.java:47)
> >>>> at
> >>>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> >>>> DefaultWagonManager.java:861)
> >>>> ... 23 more
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
> >>>>> You need to use the same id in your distribution management section
> in
> >>>>> your pom, as the server settings you want to use from server.xml. In
> >>>>> your case that would be 'remote-esp-dap-site'.
> >>>>>
> >>>>> So putting this in your pom.xml should do it:
> >>>>>
> >>>>> <distributionManagement>
> >>>>> <site>
> >>>>> <id>remote-esp-dap-site</id>
> >>>>> <name>DAP-Site</name>
> >>>>>
> >>>>> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> >>>>> </site>
> >>>>> </distributionManagement>
> >>>>>
> >>>>>
> >>>>> Mick Knutson wrote:
> >>>>>> I want to connect to a remote repository with a different user than
> >>>>>> I am when I am compiling:
> >>>>>>
> >>>>>> <server>
> >>>>>> <id>remote-esp-dap-site</id>
> >>>>>> <username>maven_user</username>
> >>>>>> <passphrase>somephrase</passphrase>
> >>>>>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> >>>>>> <configuration>
> >>>>>> <sshExecutable>plink</sshExecutable>
> >>>>>> <scpExecutable>pscp</scpExecutable>
> >>>>>> </configuration>
> >>>>>> </server>
> >>>>>>
> >>>>>>
> >>>>>> <distributionManagement>
> >>>>>> <site>
> >>>>>> <id>rc_sun66e</id>
> >>>>>> <name>DAP-Site</name>
> >>>>>> <url>scpexe://rc-sun66e.ut.dentegra.lab
> >>>>> /:/opt/htdocs/site/</url>
> >>>>>> </site>
> >>>>>> </distributionManagement>
> >>>>>>
> >>>>>>
> >>>>>> But I get this error:
> >>>>>>
> >>>>>> [INFO] [site:deploy]
> >>>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> >>>>> Session:
> >>>>>> Opened
> >>>>>> Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> >>>>>> Settings\dnxmkk5\.ssh\id_rsa"
> >>>>>> -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> >>>>>> opt/htdocs/site/utilities/."'
> >>>>>>
> >>>>>> 'ssh' is not recognized as an internal or external command,
> operable
> >>>>>> program or batch file.
> >>>>>>
> >>>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> >>>>> Session:
> >>>>>> Disconnecting
> >>>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> >>>>> Session:
> >>>>>> Disconnected
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> I want to use the maven_user not dnxmkk5 user. But there also seems
> >>>>>> to
> >>>>> be an
> >>>>>> issue with the command that is generated.
> >>>>>>
> >>>>>> I tried following these directions:
> >>>>>>
> >>>>>
> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remo
> >>>>> te.html
> >>>>>>
> >>>>> --
> >>>>> Dennis Lundberg
> >>>>>
> >>>>>
> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: users-help@maven.apache.org
> >>>>>
> >>>>>
> >>>> --
> >>>>
> >>>> Thanks,
> >>>> Mick Knutson
> >>>>
> >>>> http://www.baselogic.com
> >>>> http://www.blincmagazine.com
> >>>> http://www.djmick.com
> >>>> http://www.myspace.com/mickknutson
> >>>> http://www.myspace.com/djmick_dot_com
> >>>> http://www.myspace.com/sexybeotches
> >>>> http://www.thumpradio.com
> >>>> ---
> >>>>
> >>>> Visit our website at http://www.ubs.com
> >>>>
> >>>> This message contains confidential information and is intended only
> >>>> for the individual named. If you are not the named addressee you
> >>>> should not disseminate, distribute or copy this e-mail. Please
> >>>> notify the sender immediately by e-mail if you have received this
> >>>> e-mail by mistake and delete this e-mail from your system.
> >>>>
> >>>> E-mail transmission cannot be guaranteed to be secure or error-free
> >>>> as information could be intercepted, corrupted, lost, destroyed,
> >>>> arrive late or incomplete, or contain viruses. The sender therefore
> >>>> does not accept liability for any errors or omissions in the contents
> >>>> of this message which arise as a result of e-mail transmission. If
> >>>> verification is required please request a hard-copy version. This
> >>>> message is provided for informational purposes and should not be
> >>>> construed as a solicitation or offer to buy or sell any securities or
> >>>> related financial instruments.
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> 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
> >>
> >>
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Re: [ms] issues with ssh connection to repo?
Posted by Dennis Lundberg <de...@apache.org>.
I'm not sure. I experimented with the different executables in the putty
distribution once, and still have that config in my settings.xml, but
it's commented out. I haven't had the need to use it in production since
the servers I deploy to works happily using scp:
Mick Knutson wrote:
> Awesome. So should I use plink for site & repo? as it putty seemed to work
> for the site already.
>
>
> On 11/8/07, Dennis Lundberg <de...@apache.org> wrote:
>> Just a tip to help debug this: use different id:s for the site and the
>> repository. Here at Apache we uses the id:s "apache.site" and
>> "apache.releases" respectively. That way the configurations are sure to
>> not intertwine with each other.
>>
>> I think you should use plink instead of putty for your <sshExecutable>
>>
>> Mick Knutson wrote:
>>> :-O this is crazy.
>>>
>>> so for site 'scp:' works, but for the repo, I need to use 'scpexe:'....
>>>
>>> Ok, I did that, then putty opened and alert dialog saying "invalid
>> option
>>> -o"
>>> I clicked Ok, then there was this error:
>>>
>>> [INFO] [deploy:deploy]
>>> altDeploymentRepository = null
>>> [INFO] Retrieving previous build number from rc_sun66e
>>> Uploading: scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
>>> /org/delta/esp/dap/E1B-1.0-SNAPSHOT/dap-E1B-1.0-20071108.191732-1.pom
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error deploying artifact: Error executing command for transfer
>>>
>>> Exit code 1 -
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
>>> artifact: Error executing command for transfer
>>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>> DefaultLifecycleExecutor.java:564)
>>> at
>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
>>> (DefaultLifecycleExecutor.java:480)
>>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>>> DefaultLifecycleExecutor.java:459)
>>> at
>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
>>> (DefaultLifecycleExecutor.java:311)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>>> DefaultLifecycleExecutor.java:278)
>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>>> DefaultLifecycleExecutor.java:143)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
>> :334)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>>> 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:585)
>>> 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.plugin.MojoExecutionException: Error
>> deploying
>>> artifact: Error executing command for transfer
>>> at org.apache.maven.plugin.deploy.DeployMojo.execute(
>> DeployMojo.java
>>> :174)
>>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>>> DefaultPluginManager.java:443)
>>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>> DefaultLifecycleExecutor.java:539)
>>> ... 16 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:94)
>>> at org.apache.maven.plugin.deploy.DeployMojo.execute(
>> DeployMojo.java
>>> :152)
>>> ... 18 more
>>> Caused by: org.apache.maven.wagon.TransferFailedException: Error
>> executing
>>> command for transfer
>>> at
>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
>>> ScpExternalWagon.java:290)
>>> at
>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
>>> DefaultWagonManager.java:237)
>>> at
>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
>>> (DefaultWagonManager.java:153)
>>> at
>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
>>> (DefaultArtifactDeployer.java:80)
>>> ... 19 more
>>> Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code 1
>> -
>>> at
>>>
>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
>>> (ScpExternalWagon.java:145)
>>> at
>>>
>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
>>> (ScpExternalWagon.java:326)
>>> at
>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
>>> ScpExternalWagon.java:286)
>>>
>>>
>>>
>>> I got the above error when I tried this URL formats:
>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
>>> or
>>> scpexe://rc-sun66e.ut.dentegra.lab/opt/htdocs/repository
>>>
>>>
>>>
>>>
>>> On 11/8/07, Blue.Thomas@ubs.com <Bl...@ubs.com> wrote:
>>>> You had it right before; Replace
>>>> <url>scp:.. With
>>>> <url>scpexe:..
>>>>
>>>> under <distributionManagement>
>>>>
>>>> -----Original Message-----
>>>> From: Mick Knutson [mailto:mickknutson@gmail.com]
>>>> Sent: Thursday, November 08, 2007 1:54 PM
>>>> To: Maven Users List
>>>> Subject: Re: [ms] issues with ssh connection to repo?
>>>>
>>>> I spoke too soon.
>>>> I have the 'mvn site-deploy' working with the following server:
>>>>
>>>>
>>>>
>>>>
>>>> <server>
>>>> <id>rc_sun66e</id>
>>>> <username>[username]</username>
>>>> <password>[password]</password>
>>>> <passphrase>[phrase]</passphrase>
>>>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
>>>> <configuration>
>>>> <sshExecutable>putty</sshExecutable> <!-- also tried
>>>> plink
>>>> -->
>>>> <scpExecutable>pscp</scpExecutable>
>>>> </configuration>
>>>> </server>
>>>>
>>>> Then I have this:
>>>>
>>>> <distributionManagement>
>>>> <site>
>>>> <id>rc_sun66e</id>
>>>> <name>DAP-Site</name>
>>>> <url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
>>>> project.version}</url>
>>>> </site>
>>>>
>>>> <!-- use the following if you're not using a snapshot version.
>>>> -->
>>>> <repository>
>>>> <id>rc_sun66e</id>
>>>> <name>DAP-Repository</name>
>>>> <url>scp://rc-sun66e.ut.dentegra.lab
>>>> /:/opt/htdocs/repository</url>
>>>> </repository>
>>>> </distributionManagement>
>>>>
>>>>
>>>> So if the site works fine, why do I get this with 'mvn clean deploy
>> -e':
>>>> [INFO] [deploy:deploy]
>>>> altDeploymentRepository = null
>>>> [INFO] Retrieving previous build number from rc_sun66e [WARNING]
>>>> repository metadata for: 'snapshot org.delta.esp:dap:E1B-1.0-SNAPSHOT'
>>>> could not be retrieved from repository:
>>>> rc_sun66e due to an error: While c
>>>> onfiguring wagon for 'rc_sun66e': Unable to apply wagon configuration.
>>>> [INFO] Repository 'rc_sun66e' will be blacklisted [INFO]
>>>>
>> ------------------------------------------------------------------------
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>>
>> ------------------------------------------------------------------------
>>>> [INFO] Error deploying artifact: While configuring wagon for
>>>> 'rc_sun66e':
>>>> Unable to apply wagon configuration.
>>>>
>>>> Cannot find setter nor field in
>>>> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
>>>> [INFO]
>>>>
>> ------------------------------------------------------------------------
>>>> [INFO] Trace
>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
>>>> artifact: While configuring wagon for 'rc_sun66e': Unable to apply
>> wagon
>>>> configuration.
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>>> DefaultLifecycleExecutor.java:564)
>>>> at
>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
>>>> ycle
>>>> (DefaultLifecycleExecutor.java:480)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>>>> DefaultLifecycleExecutor.java:459)
>>>> at
>>>>
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
>>>> Failures
>>>> (DefaultLifecycleExecutor.java:311)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
>> (
>>>> DefaultLifecycleExecutor.java:278)
>>>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>>>> DefaultLifecycleExecutor.java:143)
>>>> at
>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>>>> 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:585)
>>>> 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.plugin.MojoExecutionException: Error
>>>> deploying
>>>> artifact: While configuring wagon for 'rc_sun66e': Unable to apply
>> wagon
>>>> configu ration.
>>>> at
>>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
>>>> :174)
>>>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>>>> DefaultPluginManager.java:443)
>>>> at
>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>>>> DefaultLifecycleExecutor.java:539)
>>>> ... 16 more
>>>> Caused by:
>>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>> Error deploying artifact: While configuring wagon for 'rc_sun66e':
>>>> Unable to app ly wagon configuration.
>>>> at
>>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
>>>> (DefaultArtifactDeployer.java:94)
>>>> at
>>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
>>>> :152)
>>>> ... 18 more
>>>> Caused by:
>>>> org.apache.maven.artifact.manager.WagonConfigurationException:
>>>> While configuring wagon for 'rc_sun66e': Unable to apply wagon
>>>> configuration.
>>>> at
>>>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
>>>> DefaultWagonManager.java:872)
>>>> at
>>>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
>>>> DefaultWagonManager.java:848)
>>>> at
>>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
>>>> DefaultWagonManager.java:180)
>>>> at
>>>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
>>>> (DefaultWagonManager.java:153)
>>>> at
>>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
>>>> (DefaultArtifactDeployer.java:80)
>>>> ... 19 more
>>>> Caused by:
>>>>
>> org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
>>>> on:
>>>> Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
>>>> .jsch.ScpWagon for 'sshExecutable'
>>>> at
>>>>
>> org.codehaus.plexus.component.configurator.converters.ComponentValueSett
>>>> er
>>>> .<init>(ComponentValueSetter.java:68)
>>>> at
>>>>
>> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
>>>> thFieldsConverter.processConfiguration
>>>> (ObjectWithFieldsConverter.java:13
>>>> 4)
>>>> at
>>>>
>> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
>>>> nfigureComponent
>>>> (BasicComponentConfigurator.java:56)
>>>> at
>>>>
>> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
>>>> .configureComponent
>>>> (AbstractComponentConfigurator.java:54)
>>>> at
>>>>
>> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
>>>> .configureComponent
>>>> (AbstractComponentConfigurator.java:47)
>>>> at
>>>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
>>>> DefaultWagonManager.java:861)
>>>> ... 23 more
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
>>>>> You need to use the same id in your distribution management section in
>>>>> your pom, as the server settings you want to use from server.xml. In
>>>>> your case that would be 'remote-esp-dap-site'.
>>>>>
>>>>> So putting this in your pom.xml should do it:
>>>>>
>>>>> <distributionManagement>
>>>>> <site>
>>>>> <id>remote-esp-dap-site</id>
>>>>> <name>DAP-Site</name>
>>>>>
>>>>> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
>>>>> </site>
>>>>> </distributionManagement>
>>>>>
>>>>>
>>>>> Mick Knutson wrote:
>>>>>> I want to connect to a remote repository with a different user than
>>>>>> I am when I am compiling:
>>>>>>
>>>>>> <server>
>>>>>> <id>remote-esp-dap-site</id>
>>>>>> <username>maven_user</username>
>>>>>> <passphrase>somephrase</passphrase>
>>>>>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
>>>>>> <configuration>
>>>>>> <sshExecutable>plink</sshExecutable>
>>>>>> <scpExecutable>pscp</scpExecutable>
>>>>>> </configuration>
>>>>>> </server>
>>>>>>
>>>>>>
>>>>>> <distributionManagement>
>>>>>> <site>
>>>>>> <id>rc_sun66e</id>
>>>>>> <name>DAP-Site</name>
>>>>>> <url>scpexe://rc-sun66e.ut.dentegra.lab
>>>>> /:/opt/htdocs/site/</url>
>>>>>> </site>
>>>>>> </distributionManagement>
>>>>>>
>>>>>>
>>>>>> But I get this error:
>>>>>>
>>>>>> [INFO] [site:deploy]
>>>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
>>>>> Session:
>>>>>> Opened
>>>>>> Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
>>>>>> Settings\dnxmkk5\.ssh\id_rsa"
>>>>>> -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
>>>>>> opt/htdocs/site/utilities/."'
>>>>>>
>>>>>> 'ssh' is not recognized as an internal or external command, operable
>>>>>> program or batch file.
>>>>>>
>>>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
>>>>> Session:
>>>>>> Disconnecting
>>>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
>>>>> Session:
>>>>>> Disconnected
>>>>>>
>>>>>>
>>>>>>
>>>>>> I want to use the maven_user not dnxmkk5 user. But there also seems
>>>>>> to
>>>>> be an
>>>>>> issue with the command that is generated.
>>>>>>
>>>>>> I tried following these directions:
>>>>>>
>>>>> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remo
>>>>> te.html
>>>>>>
>>>>> --
>>>>> Dennis Lundberg
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>> --
>>>>
>>>> Thanks,
>>>> Mick Knutson
>>>>
>>>> http://www.baselogic.com
>>>> http://www.blincmagazine.com
>>>> http://www.djmick.com
>>>> http://www.myspace.com/mickknutson
>>>> http://www.myspace.com/djmick_dot_com
>>>> http://www.myspace.com/sexybeotches
>>>> http://www.thumpradio.com
>>>> ---
>>>>
>>>> Visit our website at http://www.ubs.com
>>>>
>>>> This message contains confidential information and is intended only
>>>> for the individual named. If you are not the named addressee you
>>>> should not disseminate, distribute or copy this e-mail. Please
>>>> notify the sender immediately by e-mail if you have received this
>>>> e-mail by mistake and delete this e-mail from your system.
>>>>
>>>> E-mail transmission cannot be guaranteed to be secure or error-free
>>>> as information could be intercepted, corrupted, lost, destroyed,
>>>> arrive late or incomplete, or contain viruses. The sender therefore
>>>> does not accept liability for any errors or omissions in the contents
>>>> of this message which arise as a result of e-mail transmission. If
>>>> verification is required please request a hard-copy version. This
>>>> message is provided for informational purposes and should not be
>>>> construed as a solicitation or offer to buy or sell any securities or
>>>> related financial instruments.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
>>
>>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ms] issues with ssh connection to repo?
Posted by Mick Knutson <mi...@gmail.com>.
Awesome. So should I use plink for site & repo? as it putty seemed to work
for the site already.
On 11/8/07, Dennis Lundberg <de...@apache.org> wrote:
>
> Just a tip to help debug this: use different id:s for the site and the
> repository. Here at Apache we uses the id:s "apache.site" and
> "apache.releases" respectively. That way the configurations are sure to
> not intertwine with each other.
>
> I think you should use plink instead of putty for your <sshExecutable>
>
> Mick Knutson wrote:
> > :-O this is crazy.
> >
> > so for site 'scp:' works, but for the repo, I need to use 'scpexe:'....
> >
> > Ok, I did that, then putty opened and alert dialog saying "invalid
> option
> > -o"
> > I clicked Ok, then there was this error:
> >
> > [INFO] [deploy:deploy]
> > altDeploymentRepository = null
> > [INFO] Retrieving previous build number from rc_sun66e
> > Uploading: scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
> > /org/delta/esp/dap/E1B-1.0-SNAPSHOT/dap-E1B-1.0-20071108.191732-1.pom
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Error deploying artifact: Error executing command for transfer
> >
> > Exit code 1 -
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Trace
> > org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> > artifact: Error executing command for transfer
> > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> > DefaultLifecycleExecutor.java:564)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> > (DefaultLifecycleExecutor.java:480)
> > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> > DefaultLifecycleExecutor.java:459)
> > at
> >
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> > (DefaultLifecycleExecutor.java:311)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> > DefaultLifecycleExecutor.java:278)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> > DefaultLifecycleExecutor.java:143)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
> :334)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> > 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:585)
> > 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.plugin.MojoExecutionException: Error
> deploying
> > artifact: Error executing command for transfer
> > at org.apache.maven.plugin.deploy.DeployMojo.execute(
> DeployMojo.java
> > :174)
> > at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> > DefaultPluginManager.java:443)
> > at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> > DefaultLifecycleExecutor.java:539)
> > ... 16 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:94)
> > at org.apache.maven.plugin.deploy.DeployMojo.execute(
> DeployMojo.java
> > :152)
> > ... 18 more
> > Caused by: org.apache.maven.wagon.TransferFailedException: Error
> executing
> > command for transfer
> > at
> > org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
> > ScpExternalWagon.java:290)
> > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
> > DefaultWagonManager.java:237)
> > at
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
> > (DefaultWagonManager.java:153)
> > at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> > (DefaultArtifactDeployer.java:80)
> > ... 19 more
> > Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code 1
> -
> > at
> >
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
> > (ScpExternalWagon.java:145)
> > at
> >
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
> > (ScpExternalWagon.java:326)
> > at
> > org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
> > ScpExternalWagon.java:286)
> >
> >
> >
> > I got the above error when I tried this URL formats:
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
> > or
> > scpexe://rc-sun66e.ut.dentegra.lab/opt/htdocs/repository
> >
> >
> >
> >
> > On 11/8/07, Blue.Thomas@ubs.com <Bl...@ubs.com> wrote:
> >> You had it right before; Replace
> >> <url>scp:.. With
> >> <url>scpexe:..
> >>
> >> under <distributionManagement>
> >>
> >> -----Original Message-----
> >> From: Mick Knutson [mailto:mickknutson@gmail.com]
> >> Sent: Thursday, November 08, 2007 1:54 PM
> >> To: Maven Users List
> >> Subject: Re: [ms] issues with ssh connection to repo?
> >>
> >> I spoke too soon.
> >> I have the 'mvn site-deploy' working with the following server:
> >>
> >>
> >>
> >>
> >> <server>
> >> <id>rc_sun66e</id>
> >> <username>[username]</username>
> >> <password>[password]</password>
> >> <passphrase>[phrase]</passphrase>
> >> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> >> <configuration>
> >> <sshExecutable>putty</sshExecutable> <!-- also tried
> >> plink
> >> -->
> >> <scpExecutable>pscp</scpExecutable>
> >> </configuration>
> >> </server>
> >>
> >> Then I have this:
> >>
> >> <distributionManagement>
> >> <site>
> >> <id>rc_sun66e</id>
> >> <name>DAP-Site</name>
> >> <url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
> >> project.version}</url>
> >> </site>
> >>
> >> <!-- use the following if you're not using a snapshot version.
> >> -->
> >> <repository>
> >> <id>rc_sun66e</id>
> >> <name>DAP-Repository</name>
> >> <url>scp://rc-sun66e.ut.dentegra.lab
> >> /:/opt/htdocs/repository</url>
> >> </repository>
> >> </distributionManagement>
> >>
> >>
> >> So if the site works fine, why do I get this with 'mvn clean deploy
> -e':
> >>
> >> [INFO] [deploy:deploy]
> >> altDeploymentRepository = null
> >> [INFO] Retrieving previous build number from rc_sun66e [WARNING]
> >> repository metadata for: 'snapshot org.delta.esp:dap:E1B-1.0-SNAPSHOT'
> >> could not be retrieved from repository:
> >> rc_sun66e due to an error: While c
> >> onfiguring wagon for 'rc_sun66e': Unable to apply wagon configuration.
> >> [INFO] Repository 'rc_sun66e' will be blacklisted [INFO]
> >>
> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >>
> ------------------------------------------------------------------------
> >> [INFO] Error deploying artifact: While configuring wagon for
> >> 'rc_sun66e':
> >> Unable to apply wagon configuration.
> >>
> >> Cannot find setter nor field in
> >> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
> >> [INFO]
> >>
> ------------------------------------------------------------------------
> >> [INFO] Trace
> >> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> >> artifact: While configuring wagon for 'rc_sun66e': Unable to apply
> wagon
> >> configuration.
> >> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> >> DefaultLifecycleExecutor.java:564)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> >> ycle
> >> (DefaultLifecycleExecutor.java:480)
> >> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> >> DefaultLifecycleExecutor.java:459)
> >> at
> >>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> >> Failures
> >> (DefaultLifecycleExecutor.java:311)
> >> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments
> (
> >> DefaultLifecycleExecutor.java:278)
> >> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> >> DefaultLifecycleExecutor.java:143)
> >> at
> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> >> 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:585)
> >> 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.plugin.MojoExecutionException: Error
> >> deploying
> >> artifact: While configuring wagon for 'rc_sun66e': Unable to apply
> wagon
> >> configu ration.
> >> at
> >> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> >> :174)
> >> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> >> DefaultPluginManager.java:443)
> >> at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> >> DefaultLifecycleExecutor.java:539)
> >> ... 16 more
> >> Caused by:
> >> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> >> Error deploying artifact: While configuring wagon for 'rc_sun66e':
> >> Unable to app ly wagon configuration.
> >> at
> >> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> >> (DefaultArtifactDeployer.java:94)
> >> at
> >> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> >> :152)
> >> ... 18 more
> >> Caused by:
> >> org.apache.maven.artifact.manager.WagonConfigurationException:
> >> While configuring wagon for 'rc_sun66e': Unable to apply wagon
> >> configuration.
> >> at
> >> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> >> DefaultWagonManager.java:872)
> >> at
> >> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> >> DefaultWagonManager.java:848)
> >> at
> >> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
> >> DefaultWagonManager.java:180)
> >> at
> >> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
> >> (DefaultWagonManager.java:153)
> >> at
> >> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> >> (DefaultArtifactDeployer.java:80)
> >> ... 19 more
> >> Caused by:
> >>
> org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
> >> on:
> >> Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
> >> .jsch.ScpWagon for 'sshExecutable'
> >> at
> >>
> org.codehaus.plexus.component.configurator.converters.ComponentValueSett
> >> er
> >> .<init>(ComponentValueSetter.java:68)
> >> at
> >>
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
> >> thFieldsConverter.processConfiguration
> >> (ObjectWithFieldsConverter.java:13
> >> 4)
> >> at
> >>
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
> >> nfigureComponent
> >> (BasicComponentConfigurator.java:56)
> >> at
> >>
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
> >> .configureComponent
> >> (AbstractComponentConfigurator.java:54)
> >> at
> >>
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
> >> .configureComponent
> >> (AbstractComponentConfigurator.java:47)
> >> at
> >> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> >> DefaultWagonManager.java:861)
> >> ... 23 more
> >>
> >>
> >>
> >>
> >>
> >> On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
> >>> You need to use the same id in your distribution management section in
> >>> your pom, as the server settings you want to use from server.xml. In
> >>> your case that would be 'remote-esp-dap-site'.
> >>>
> >>> So putting this in your pom.xml should do it:
> >>>
> >>> <distributionManagement>
> >>> <site>
> >>> <id>remote-esp-dap-site</id>
> >>> <name>DAP-Site</name>
> >>>
> >>> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> >>> </site>
> >>> </distributionManagement>
> >>>
> >>>
> >>> Mick Knutson wrote:
> >>>> I want to connect to a remote repository with a different user than
> >>>> I am when I am compiling:
> >>>>
> >>>> <server>
> >>>> <id>remote-esp-dap-site</id>
> >>>> <username>maven_user</username>
> >>>> <passphrase>somephrase</passphrase>
> >>>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> >>>> <configuration>
> >>>> <sshExecutable>plink</sshExecutable>
> >>>> <scpExecutable>pscp</scpExecutable>
> >>>> </configuration>
> >>>> </server>
> >>>>
> >>>>
> >>>> <distributionManagement>
> >>>> <site>
> >>>> <id>rc_sun66e</id>
> >>>> <name>DAP-Site</name>
> >>>> <url>scpexe://rc-sun66e.ut.dentegra.lab
> >>> /:/opt/htdocs/site/</url>
> >>>> </site>
> >>>> </distributionManagement>
> >>>>
> >>>>
> >>>> But I get this error:
> >>>>
> >>>> [INFO] [site:deploy]
> >>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> >>> Session:
> >>>> Opened
> >>>> Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> >>>> Settings\dnxmkk5\.ssh\id_rsa"
> >>>> -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> >>>> opt/htdocs/site/utilities/."'
> >>>>
> >>>> 'ssh' is not recognized as an internal or external command, operable
> >>>> program or batch file.
> >>>>
> >>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> >>> Session:
> >>>> Disconnecting
> >>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> >>> Session:
> >>>> Disconnected
> >>>>
> >>>>
> >>>>
> >>>> I want to use the maven_user not dnxmkk5 user. But there also seems
> >>>> to
> >>> be an
> >>>> issue with the command that is generated.
> >>>>
> >>>> I tried following these directions:
> >>>>
> >>> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remo
> >>> te.html
> >>>>
> >>>>
> >>>
> >>> --
> >>> Dennis Lundberg
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>>
> >>
> >> --
> >>
> >> Thanks,
> >> Mick Knutson
> >>
> >> http://www.baselogic.com
> >> http://www.blincmagazine.com
> >> http://www.djmick.com
> >> http://www.myspace.com/mickknutson
> >> http://www.myspace.com/djmick_dot_com
> >> http://www.myspace.com/sexybeotches
> >> http://www.thumpradio.com
> >> ---
> >>
> >> Visit our website at http://www.ubs.com
> >>
> >> This message contains confidential information and is intended only
> >> for the individual named. If you are not the named addressee you
> >> should not disseminate, distribute or copy this e-mail. Please
> >> notify the sender immediately by e-mail if you have received this
> >> e-mail by mistake and delete this e-mail from your system.
> >>
> >> E-mail transmission cannot be guaranteed to be secure or error-free
> >> as information could be intercepted, corrupted, lost, destroyed,
> >> arrive late or incomplete, or contain viruses. The sender therefore
> >> does not accept liability for any errors or omissions in the contents
> >> of this message which arise as a result of e-mail transmission. If
> >> verification is required please request a hard-copy version. This
> >> message is provided for informational purposes and should not be
> >> construed as a solicitation or offer to buy or sell any securities or
> >> related financial instruments.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Re: [ms] issues with ssh connection to repo?
Posted by Dennis Lundberg <de...@apache.org>.
Just a tip to help debug this: use different id:s for the site and the
repository. Here at Apache we uses the id:s "apache.site" and
"apache.releases" respectively. That way the configurations are sure to
not intertwine with each other.
I think you should use plink instead of putty for your <sshExecutable>
Mick Knutson wrote:
> :-O this is crazy.
>
> so for site 'scp:' works, but for the repo, I need to use 'scpexe:'....
>
> Ok, I did that, then putty opened and alert dialog saying "invalid option
> -o"
> I clicked Ok, then there was this error:
>
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from rc_sun66e
> Uploading: scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
> /org/delta/esp/dap/E1B-1.0-SNAPSHOT/dap-E1B-1.0-20071108.191732-1.pom
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Error executing command for transfer
>
> Exit code 1 -
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> artifact: Error executing command for transfer
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:480)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:278)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:143)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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:585)
> 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.plugin.MojoExecutionException: Error deploying
> artifact: Error executing command for transfer
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> :174)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:539)
> ... 16 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:94)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> :152)
> ... 18 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Error executing
> command for transfer
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
> ScpExternalWagon.java:290)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
> DefaultWagonManager.java:237)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
> (DefaultWagonManager.java:153)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:80)
> ... 19 more
> Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code 1 -
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
> (ScpExternalWagon.java:145)
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
> (ScpExternalWagon.java:326)
> at
> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
> ScpExternalWagon.java:286)
>
>
>
> I got the above error when I tried this URL formats:
> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
> or
> scpexe://rc-sun66e.ut.dentegra.lab/opt/htdocs/repository
>
>
>
>
> On 11/8/07, Blue.Thomas@ubs.com <Bl...@ubs.com> wrote:
>> You had it right before; Replace
>> <url>scp:.. With
>> <url>scpexe:..
>>
>> under <distributionManagement>
>>
>> -----Original Message-----
>> From: Mick Knutson [mailto:mickknutson@gmail.com]
>> Sent: Thursday, November 08, 2007 1:54 PM
>> To: Maven Users List
>> Subject: Re: [ms] issues with ssh connection to repo?
>>
>> I spoke too soon.
>> I have the 'mvn site-deploy' working with the following server:
>>
>>
>>
>>
>> <server>
>> <id>rc_sun66e</id>
>> <username>[username]</username>
>> <password>[password]</password>
>> <passphrase>[phrase]</passphrase>
>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
>> <configuration>
>> <sshExecutable>putty</sshExecutable> <!-- also tried
>> plink
>> -->
>> <scpExecutable>pscp</scpExecutable>
>> </configuration>
>> </server>
>>
>> Then I have this:
>>
>> <distributionManagement>
>> <site>
>> <id>rc_sun66e</id>
>> <name>DAP-Site</name>
>> <url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
>> project.version}</url>
>> </site>
>>
>> <!-- use the following if you're not using a snapshot version.
>> -->
>> <repository>
>> <id>rc_sun66e</id>
>> <name>DAP-Repository</name>
>> <url>scp://rc-sun66e.ut.dentegra.lab
>> /:/opt/htdocs/repository</url>
>> </repository>
>> </distributionManagement>
>>
>>
>> So if the site works fine, why do I get this with 'mvn clean deploy -e':
>>
>> [INFO] [deploy:deploy]
>> altDeploymentRepository = null
>> [INFO] Retrieving previous build number from rc_sun66e [WARNING]
>> repository metadata for: 'snapshot org.delta.esp:dap:E1B-1.0-SNAPSHOT'
>> could not be retrieved from repository:
>> rc_sun66e due to an error: While c
>> onfiguring wagon for 'rc_sun66e': Unable to apply wagon configuration.
>> [INFO] Repository 'rc_sun66e' will be blacklisted [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Error deploying artifact: While configuring wagon for
>> 'rc_sun66e':
>> Unable to apply wagon configuration.
>>
>> Cannot find setter nor field in
>> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
>> artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
>> configuration.
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> DefaultLifecycleExecutor.java:564)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
>> ycle
>> (DefaultLifecycleExecutor.java:480)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>> DefaultLifecycleExecutor.java:459)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
>> Failures
>> (DefaultLifecycleExecutor.java:311)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>> DefaultLifecycleExecutor.java:278)
>> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>> DefaultLifecycleExecutor.java:143)
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>> 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:585)
>> 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.plugin.MojoExecutionException: Error
>> deploying
>> artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
>> configu ration.
>> at
>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
>> :174)
>> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>> DefaultPluginManager.java:443)
>> at
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> DefaultLifecycleExecutor.java:539)
>> ... 16 more
>> Caused by:
>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>> Error deploying artifact: While configuring wagon for 'rc_sun66e':
>> Unable to app ly wagon configuration.
>> at
>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
>> (DefaultArtifactDeployer.java:94)
>> at
>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
>> :152)
>> ... 18 more
>> Caused by:
>> org.apache.maven.artifact.manager.WagonConfigurationException:
>> While configuring wagon for 'rc_sun66e': Unable to apply wagon
>> configuration.
>> at
>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
>> DefaultWagonManager.java:872)
>> at
>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
>> DefaultWagonManager.java:848)
>> at
>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
>> DefaultWagonManager.java:180)
>> at
>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
>> (DefaultWagonManager.java:153)
>> at
>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
>> (DefaultArtifactDeployer.java:80)
>> ... 19 more
>> Caused by:
>> org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
>> on:
>> Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
>> .jsch.ScpWagon for 'sshExecutable'
>> at
>> org.codehaus.plexus.component.configurator.converters.ComponentValueSett
>> er
>> .<init>(ComponentValueSetter.java:68)
>> at
>> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
>> thFieldsConverter.processConfiguration
>> (ObjectWithFieldsConverter.java:13
>> 4)
>> at
>> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
>> nfigureComponent
>> (BasicComponentConfigurator.java:56)
>> at
>> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
>> .configureComponent
>> (AbstractComponentConfigurator.java:54)
>> at
>> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
>> .configureComponent
>> (AbstractComponentConfigurator.java:47)
>> at
>> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
>> DefaultWagonManager.java:861)
>> ... 23 more
>>
>>
>>
>>
>>
>> On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
>>> You need to use the same id in your distribution management section in
>>> your pom, as the server settings you want to use from server.xml. In
>>> your case that would be 'remote-esp-dap-site'.
>>>
>>> So putting this in your pom.xml should do it:
>>>
>>> <distributionManagement>
>>> <site>
>>> <id>remote-esp-dap-site</id>
>>> <name>DAP-Site</name>
>>>
>>> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
>>> </site>
>>> </distributionManagement>
>>>
>>>
>>> Mick Knutson wrote:
>>>> I want to connect to a remote repository with a different user than
>>>> I am when I am compiling:
>>>>
>>>> <server>
>>>> <id>remote-esp-dap-site</id>
>>>> <username>maven_user</username>
>>>> <passphrase>somephrase</passphrase>
>>>> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
>>>> <configuration>
>>>> <sshExecutable>plink</sshExecutable>
>>>> <scpExecutable>pscp</scpExecutable>
>>>> </configuration>
>>>> </server>
>>>>
>>>>
>>>> <distributionManagement>
>>>> <site>
>>>> <id>rc_sun66e</id>
>>>> <name>DAP-Site</name>
>>>> <url>scpexe://rc-sun66e.ut.dentegra.lab
>>> /:/opt/htdocs/site/</url>
>>>> </site>
>>>> </distributionManagement>
>>>>
>>>>
>>>> But I get this error:
>>>>
>>>> [INFO] [site:deploy]
>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
>>> Session:
>>>> Opened
>>>> Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
>>>> Settings\dnxmkk5\.ssh\id_rsa"
>>>> -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
>>>> opt/htdocs/site/utilities/."'
>>>>
>>>> 'ssh' is not recognized as an internal or external command, operable
>>>> program or batch file.
>>>>
>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
>>> Session:
>>>> Disconnecting
>>>> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
>>> Session:
>>>> Disconnected
>>>>
>>>>
>>>>
>>>> I want to use the maven_user not dnxmkk5 user. But there also seems
>>>> to
>>> be an
>>>> issue with the command that is generated.
>>>>
>>>> I tried following these directions:
>>>>
>>> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remo
>>> te.html
>>>>
>>>>
>>>
>>> --
>>> Dennis Lundberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>> --
>>
>> Thanks,
>> Mick Knutson
>>
>> http://www.baselogic.com
>> http://www.blincmagazine.com
>> http://www.djmick.com
>> http://www.myspace.com/mickknutson
>> http://www.myspace.com/djmick_dot_com
>> http://www.myspace.com/sexybeotches
>> http://www.thumpradio.com
>> ---
>>
>> Visit our website at http://www.ubs.com
>>
>> This message contains confidential information and is intended only
>> for the individual named. If you are not the named addressee you
>> should not disseminate, distribute or copy this e-mail. Please
>> notify the sender immediately by e-mail if you have received this
>> e-mail by mistake and delete this e-mail from your system.
>>
>> E-mail transmission cannot be guaranteed to be secure or error-free
>> as information could be intercepted, corrupted, lost, destroyed,
>> arrive late or incomplete, or contain viruses. The sender therefore
>> does not accept liability for any errors or omissions in the contents
>> of this message which arise as a result of e-mail transmission. If
>> verification is required please request a hard-copy version. This
>> message is provided for informational purposes and should not be
>> construed as a solicitation or offer to buy or sell any securities or
>> related financial instruments.
>>
>>
>> ---------------------------------------------------------------------
>> 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: [ms] issues with ssh connection to repo?
Posted by Mick Knutson <mi...@gmail.com>.
:-O this is crazy.
so for site 'scp:' works, but for the repo, I need to use 'scpexe:'....
Ok, I did that, then putty opened and alert dialog saying "invalid option
-o"
I clicked Ok, then there was this error:
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from rc_sun66e
Uploading: scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
/org/delta/esp/dap/E1B-1.0-SNAPSHOT/dap-E1B-1.0-20071108.191732-1.pom
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: Error executing command for transfer
Exit code 1 -
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Error executing command for transfer
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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:585)
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.plugin.MojoExecutionException: Error deploying
artifact: Error executing command for transfer
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
:174)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:539)
... 16 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:94)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
:152)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Error executing
command for transfer
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
ScpExternalWagon.java:290)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
DefaultWagonManager.java:237)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
(DefaultWagonManager.java:153)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:80)
... 19 more
Caused by: org.apache.maven.wagon.CommandExecutionException: Exit code 1 -
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
(ScpExternalWagon.java:145)
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeCommand
(ScpExternalWagon.java:326)
at
org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(
ScpExternalWagon.java:286)
I got the above error when I tried this URL formats:
scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/repository
or
scpexe://rc-sun66e.ut.dentegra.lab/opt/htdocs/repository
On 11/8/07, Blue.Thomas@ubs.com <Bl...@ubs.com> wrote:
>
> You had it right before; Replace
> <url>scp:.. With
> <url>scpexe:..
>
> under <distributionManagement>
>
> -----Original Message-----
> From: Mick Knutson [mailto:mickknutson@gmail.com]
> Sent: Thursday, November 08, 2007 1:54 PM
> To: Maven Users List
> Subject: Re: [ms] issues with ssh connection to repo?
>
> I spoke too soon.
> I have the 'mvn site-deploy' working with the following server:
>
>
>
>
> <server>
> <id>rc_sun66e</id>
> <username>[username]</username>
> <password>[password]</password>
> <passphrase>[phrase]</passphrase>
> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> <configuration>
> <sshExecutable>putty</sshExecutable> <!-- also tried
> plink
> -->
> <scpExecutable>pscp</scpExecutable>
> </configuration>
> </server>
>
> Then I have this:
>
> <distributionManagement>
> <site>
> <id>rc_sun66e</id>
> <name>DAP-Site</name>
> <url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
> project.version}</url>
> </site>
>
> <!-- use the following if you're not using a snapshot version.
> -->
> <repository>
> <id>rc_sun66e</id>
> <name>DAP-Repository</name>
> <url>scp://rc-sun66e.ut.dentegra.lab
> /:/opt/htdocs/repository</url>
> </repository>
> </distributionManagement>
>
>
> So if the site works fine, why do I get this with 'mvn clean deploy -e':
>
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from rc_sun66e [WARNING]
> repository metadata for: 'snapshot org.delta.esp:dap:E1B-1.0-SNAPSHOT'
> could not be retrieved from repository:
> rc_sun66e due to an error: While c
> onfiguring wagon for 'rc_sun66e': Unable to apply wagon configuration.
> [INFO] Repository 'rc_sun66e' will be blacklisted [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: While configuring wagon for
> 'rc_sun66e':
> Unable to apply wagon configuration.
>
> Cannot find setter nor field in
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
> artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
> configuration.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:564)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
> ycle
> (DefaultLifecycleExecutor.java:480)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:459)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
> Failures
> (DefaultLifecycleExecutor.java:311)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:278)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:143)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> 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:585)
> 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.plugin.MojoExecutionException: Error
> deploying
> artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
> configu ration.
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> :174)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:443)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:539)
> ... 16 more
> Caused by:
> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> Error deploying artifact: While configuring wagon for 'rc_sun66e':
> Unable to app ly wagon configuration.
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:94)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
> :152)
> ... 18 more
> Caused by:
> org.apache.maven.artifact.manager.WagonConfigurationException:
> While configuring wagon for 'rc_sun66e': Unable to apply wagon
> configuration.
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> DefaultWagonManager.java:872)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> DefaultWagonManager.java:848)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
> DefaultWagonManager.java:180)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
> (DefaultWagonManager.java:153)
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
> (DefaultArtifactDeployer.java:80)
> ... 19 more
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
> on:
> Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
> .jsch.ScpWagon for 'sshExecutable'
> at
> org.codehaus.plexus.component.configurator.converters.ComponentValueSett
> er
> .<init>(ComponentValueSetter.java:68)
> at
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
> thFieldsConverter.processConfiguration
> (ObjectWithFieldsConverter.java:13
> 4)
> at
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
> nfigureComponent
> (BasicComponentConfigurator.java:56)
> at
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
> .configureComponent
> (AbstractComponentConfigurator.java:54)
> at
> org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
> .configureComponent
> (AbstractComponentConfigurator.java:47)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
> DefaultWagonManager.java:861)
> ... 23 more
>
>
>
>
>
> On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
> >
> > You need to use the same id in your distribution management section in
>
> > your pom, as the server settings you want to use from server.xml. In
> > your case that would be 'remote-esp-dap-site'.
> >
> > So putting this in your pom.xml should do it:
> >
> > <distributionManagement>
> > <site>
> > <id>remote-esp-dap-site</id>
> > <name>DAP-Site</name>
> >
> > <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> > </site>
> > </distributionManagement>
> >
> >
> > Mick Knutson wrote:
> > > I want to connect to a remote repository with a different user than
> > > I am when I am compiling:
> > >
> > > <server>
> > > <id>remote-esp-dap-site</id>
> > > <username>maven_user</username>
> > > <passphrase>somephrase</passphrase>
> > > <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> > > <configuration>
> > > <sshExecutable>plink</sshExecutable>
> > > <scpExecutable>pscp</scpExecutable>
> > > </configuration>
> > > </server>
> > >
> > >
> > > <distributionManagement>
> > > <site>
> > > <id>rc_sun66e</id>
> > > <name>DAP-Site</name>
> > > <url>scpexe://rc-sun66e.ut.dentegra.lab
> > /:/opt/htdocs/site/</url>
> > > </site>
> > > </distributionManagement>
> > >
> > >
> > > But I get this error:
> > >
> > > [INFO] [site:deploy]
> > > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> > Session:
> > > Opened
> > > Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> > > Settings\dnxmkk5\.ssh\id_rsa"
> > > -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> > > opt/htdocs/site/utilities/."'
> > >
> > > 'ssh' is not recognized as an internal or external command, operable
>
> > > program or batch file.
> > >
> > > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> > Session:
> > > Disconnecting
> > > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> > Session:
> > > Disconnected
> > >
> > >
> > >
> > > I want to use the maven_user not dnxmkk5 user. But there also seems
> > > to
> > be an
> > > issue with the command that is generated.
> > >
> > > I tried following these directions:
> > >
> > http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remo
> > te.html
> > >
> > >
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
>
> Thanks,
> Mick Knutson
>
> http://www.baselogic.com
> http://www.blincmagazine.com
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> http://www.myspace.com/djmick_dot_com
> http://www.myspace.com/sexybeotches
> http://www.thumpradio.com
> ---
>
> Visit our website at http://www.ubs.com
>
> This message contains confidential information and is intended only
> for the individual named. If you are not the named addressee you
> should not disseminate, distribute or copy this e-mail. Please
> notify the sender immediately by e-mail if you have received this
> e-mail by mistake and delete this e-mail from your system.
>
> E-mail transmission cannot be guaranteed to be secure or error-free
> as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore
> does not accept liability for any errors or omissions in the contents
> of this message which arise as a result of e-mail transmission. If
> verification is required please request a hard-copy version. This
> message is provided for informational purposes and should not be
> construed as a solicitation or offer to buy or sell any securities or
> related financial instruments.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
RE: [ms] issues with ssh connection to repo?
Posted by Bl...@ubs.com.
You had it right before; Replace
<url>scp:.. With
<url>scpexe:..
under <distributionManagement>
-----Original Message-----
From: Mick Knutson [mailto:mickknutson@gmail.com]
Sent: Thursday, November 08, 2007 1:54 PM
To: Maven Users List
Subject: Re: [ms] issues with ssh connection to repo?
I spoke too soon.
I have the 'mvn site-deploy' working with the following server:
<server>
<id>rc_sun66e</id>
<username>[username]</username>
<password>[password]</password>
<passphrase>[phrase]</passphrase>
<privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
<configuration>
<sshExecutable>putty</sshExecutable> <!-- also tried
plink
-->
<scpExecutable>pscp</scpExecutable>
</configuration>
</server>
Then I have this:
<distributionManagement>
<site>
<id>rc_sun66e</id>
<name>DAP-Site</name>
<url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
project.version}</url>
</site>
<!-- use the following if you're not using a snapshot version.
-->
<repository>
<id>rc_sun66e</id>
<name>DAP-Repository</name>
<url>scp://rc-sun66e.ut.dentegra.lab
/:/opt/htdocs/repository</url>
</repository>
</distributionManagement>
So if the site works fine, why do I get this with 'mvn clean deploy -e':
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from rc_sun66e [WARNING]
repository metadata for: 'snapshot org.delta.esp:dap:E1B-1.0-SNAPSHOT'
could not be retrieved from repository:
rc_sun66e due to an error: While c
onfiguring wagon for 'rc_sun66e': Unable to apply wagon configuration.
[INFO] Repository 'rc_sun66e' will be blacklisted [INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: While configuring wagon for
'rc_sun66e':
Unable to apply wagon configuration.
Cannot find setter nor field in
org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
configuration.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec
ycle
(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures
(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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:585)
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.plugin.MojoExecutionException: Error
deploying
artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
configu ration.
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
:174)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:539)
... 16 more
Caused by:
org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: While configuring wagon for 'rc_sun66e':
Unable to app ly wagon configuration.
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:94)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
:152)
... 18 more
Caused by:
org.apache.maven.artifact.manager.WagonConfigurationException:
While configuring wagon for 'rc_sun66e': Unable to apply wagon
configuration.
at
org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
DefaultWagonManager.java:872)
at
org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
DefaultWagonManager.java:848)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
DefaultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
(DefaultWagonManager.java:153)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:80)
... 19 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationExcepti
on:
Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
.jsch.ScpWagon for 'sshExecutable'
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSett
er
.<init>(ComponentValueSetter.java:68)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWi
thFieldsConverter.processConfiguration
(ObjectWithFieldsConverter.java:13
4)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.co
nfigureComponent
(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent
(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator
.configureComponent
(AbstractComponentConfigurator.java:47)
at
org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
DefaultWagonManager.java:861)
... 23 more
On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
>
> You need to use the same id in your distribution management section in
> your pom, as the server settings you want to use from server.xml. In
> your case that would be 'remote-esp-dap-site'.
>
> So putting this in your pom.xml should do it:
>
> <distributionManagement>
> <site>
> <id>remote-esp-dap-site</id>
> <name>DAP-Site</name>
>
> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> </site>
> </distributionManagement>
>
>
> Mick Knutson wrote:
> > I want to connect to a remote repository with a different user than
> > I am when I am compiling:
> >
> > <server>
> > <id>remote-esp-dap-site</id>
> > <username>maven_user</username>
> > <passphrase>somephrase</passphrase>
> > <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> > <configuration>
> > <sshExecutable>plink</sshExecutable>
> > <scpExecutable>pscp</scpExecutable>
> > </configuration>
> > </server>
> >
> >
> > <distributionManagement>
> > <site>
> > <id>rc_sun66e</id>
> > <name>DAP-Site</name>
> > <url>scpexe://rc-sun66e.ut.dentegra.lab
> /:/opt/htdocs/site/</url>
> > </site>
> > </distributionManagement>
> >
> >
> > But I get this error:
> >
> > [INFO] [site:deploy]
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Opened
> > Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> > Settings\dnxmkk5\.ssh\id_rsa"
> > -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> > opt/htdocs/site/utilities/."'
> >
> > 'ssh' is not recognized as an internal or external command, operable
> > program or batch file.
> >
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Disconnecting
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Disconnected
> >
> >
> >
> > I want to use the maven_user not dnxmkk5 user. But there also seems
> > to
> be an
> > issue with the command that is generated.
> >
> > I tried following these directions:
> >
> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remo
> te.html
> >
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Visit our website at http://www.ubs.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ms] issues with ssh connection to repo?
Posted by Mick Knutson <mi...@gmail.com>.
I spoke too soon.
I have the 'mvn site-deploy' working with the following server:
<server>
<id>rc_sun66e</id>
<username>[username]</username>
<password>[password]</password>
<passphrase>[phrase]</passphrase>
<privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
<configuration>
<sshExecutable>putty</sshExecutable> <!-- also tried plink
-->
<scpExecutable>pscp</scpExecutable>
</configuration>
</server>
Then I have this:
<distributionManagement>
<site>
<id>rc_sun66e</id>
<name>DAP-Site</name>
<url>scp://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/${
project.version}</url>
</site>
<!-- use the following if you're not using a snapshot version. -->
<repository>
<id>rc_sun66e</id>
<name>DAP-Repository</name>
<url>scp://rc-sun66e.ut.dentegra.lab
/:/opt/htdocs/repository</url>
</repository>
</distributionManagement>
So if the site works fine, why do I get this with 'mvn clean deploy -e':
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from rc_sun66e
[WARNING] repository metadata for: 'snapshot
org.delta.esp:dap:E1B-1.0-SNAPSHOT' could not be retrieved from repository:
rc_sun66e due to an error: While c
onfiguring wagon for 'rc_sun66e': Unable to apply wagon configuration.
[INFO] Repository 'rc_sun66e' will be blacklisted
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: While configuring wagon for 'rc_sun66e':
Unable to apply wagon configuration.
Cannot find setter nor field in
org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
configuration.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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:585)
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.plugin.MojoExecutionException: Error deploying
artifact: While configuring wagon for 'rc_sun66e': Unable to apply wagon
configu
ration.
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
:174)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:539)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: While configuring wagon for 'rc_sun66e': Unable to
app
ly wagon configuration.
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:94)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java
:152)
... 18 more
Caused by: org.apache.maven.artifact.manager.WagonConfigurationException:
While configuring wagon for 'rc_sun66e': Unable to apply wagon
configuration.
at
org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
DefaultWagonManager.java:872)
at
org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
DefaultWagonManager.java:848)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(
DefaultWagonManager.java:180)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact
(DefaultWagonManager.java:153)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:80)
... 19 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot find setter nor field in org.apache.maven.wagon.providers.ssh
.jsch.ScpWagon for 'sshExecutable'
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter
.<init>(ComponentValueSetter.java:68)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration
(ObjectWithFieldsConverter.java:13
4)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent
(BasicComponentConfigurator.java:56)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent
(AbstractComponentConfigurator.java:54)
at
org.codehaus.plexus.component.configurator.AbstractComponentConfigurator.configureComponent
(AbstractComponentConfigurator.java:47)
at
org.apache.maven.artifact.manager.DefaultWagonManager.configureWagon(
DefaultWagonManager.java:861)
... 23 more
On 11/7/07, Dennis Lundberg <de...@apache.org> wrote:
>
> You need to use the same id in your distribution management section in
> your pom, as the server settings you want to use from server.xml. In
> your case that would be 'remote-esp-dap-site'.
>
> So putting this in your pom.xml should do it:
>
> <distributionManagement>
> <site>
> <id>remote-esp-dap-site</id>
> <name>DAP-Site</name>
>
> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> </site>
> </distributionManagement>
>
>
> Mick Knutson wrote:
> > I want to connect to a remote repository with a different user than I am
> > when I am compiling:
> >
> > <server>
> > <id>remote-esp-dap-site</id>
> > <username>maven_user</username>
> > <passphrase>somephrase</passphrase>
> > <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> > <configuration>
> > <sshExecutable>plink</sshExecutable>
> > <scpExecutable>pscp</scpExecutable>
> > </configuration>
> > </server>
> >
> >
> > <distributionManagement>
> > <site>
> > <id>rc_sun66e</id>
> > <name>DAP-Site</name>
> > <url>scpexe://rc-sun66e.ut.dentegra.lab
> /:/opt/htdocs/site/</url>
> > </site>
> > </distributionManagement>
> >
> >
> > But I get this error:
> >
> > [INFO] [site:deploy]
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Opened
> > Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> > Settings\dnxmkk5\.ssh\id_rsa"
> > -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> > opt/htdocs/site/utilities/."'
> >
> > 'ssh' is not recognized as an internal or external command,
> > operable program or batch file.
> >
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Disconnecting
> > scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities -
> Session:
> > Disconnected
> >
> >
> >
> > I want to use the maven_user not dnxmkk5 user. But there also seems to
> be an
> > issue with the command that is generated.
> >
> > I tried following these directions:
> >
> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remote.html
> >
> >
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Thanks,
Mick Knutson
http://www.baselogic.com
http://www.blincmagazine.com
http://www.djmick.com
http://www.myspace.com/mickknutson
http://www.myspace.com/djmick_dot_com
http://www.myspace.com/sexybeotches
http://www.thumpradio.com
---
Re: [ms] issues with ssh connection to repo?
Posted by Dennis Lundberg <de...@apache.org>.
You need to use the same id in your distribution management section in
your pom, as the server settings you want to use from server.xml. In
your case that would be 'remote-esp-dap-site'.
So putting this in your pom.xml should do it:
<distributionManagement>
<site>
<id>remote-esp-dap-site</id>
<name>DAP-Site</name>
<url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
</site>
</distributionManagement>
Mick Knutson wrote:
> I want to connect to a remote repository with a different user than I am
> when I am compiling:
>
> <server>
> <id>remote-esp-dap-site</id>
> <username>maven_user</username>
> <passphrase>somephrase</passphrase>
> <privateKey>c:/ssh/rc-sun66e-private.ppk</privateKey>
> <configuration>
> <sshExecutable>plink</sshExecutable>
> <scpExecutable>pscp</scpExecutable>
> </configuration>
> </server>
>
>
> <distributionManagement>
> <site>
> <id>rc_sun66e</id>
> <name>DAP-Site</name>
> <url>scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/</url>
> </site>
> </distributionManagement>
>
>
> But I get this error:
>
> [INFO] [site:deploy]
> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities - Session:
> Opened
> Executing command: cmd.exe /X /C 'ssh -i "C:\Documents and
> Settings\dnxmkk5\.ssh\id_rsa"
> -o "BatchMode yes" dnxmkk5@rc-sun66e.ut.dentegra.lab "mkdir -p ///
> opt/htdocs/site/utilities/."'
>
> 'ssh' is not recognized as an internal or external command,
> operable program or batch file.
>
> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities - Session:
> Disconnecting
> scpexe://rc-sun66e.ut.dentegra.lab/:/opt/htdocs/site/utilities - Session:
> Disconnected
>
>
>
> I want to use the maven_user not dnxmkk5 user. But there also seems to be an
> issue with the command that is generated.
>
> I tried following these directions:
> http://ekawas.blogspot.com/2007/02/maven-windows-and-deploying-to-remote.html
>
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org