Nabble - Wagon - Users

maven pom.xml deployment...

2009-11-17T15:24:15Z

Hi, all:

I'm using jahmm open source downloaded form
http://jahmm.googlecode.com/svn/repo/be/ac/ulg/montefiore/run/jahmm/jahmm/0.6.2/

As you can see, this is a maven version .

However, when I port this jahmm project into my Eclipse 3.5.1+maven 2.2.1
(I'm using m2Eclipse http://m2eclipse.sonatype.org/ )

pom.xml always indicate the following error message:

"
*POM 'org.jvnet.wagon-svn:wagon-svn' not found in repository: Unable to
download the artifact from any repository

org.jvnet.wagon-svn:wagon-svn:pom:1.8

from the specified remote repositories:
central (http://repo1.maven.org/maven2)
for project org.jvnet.wagon-svn:wagon-svn*
"

I'm wondering how to revise it to make the pom.xml compilable without those
"red crosses" error messages?

Best Regards
JIA

--
Welcome to Vision Open
http://www.visionopen.com

Welcome to Vision Open
http://www.visionopen.com

Re: What's happened to wagon's sshExecutable setting?

2009-09-10T08:18:38Z

It used to be on the site, but it seems the page is gone now...

On 11/09/2009, at 12:18 AM, Daniel Serodio wrote:

>
> Great! Thanks for the tip. Is this documented somewhere I couldn't
> find?
>
> Regards,
> Daniel Serodio
>
> brettporter wrote:
>>
>> You need to use scpexe:// for the URL instead of scp://
>>
>> - Brett
>>
>> On 10/09/2009, at 6:09 AM, Daniel Serodio wrote:
>>
>>>
>>> I'm on Windows XP, and I'm trying to make Maven deployment use my
>>> private key
>>> which is stored in PuTTY's Pageant ssh agent.
>>>
>>> I found an old recipe on the net that says I should use the
>>> following
>>> settings.xml:
>>>
>>> <server>
>>> <id>my-repo</id>
>>> <configuration>
>>> <sshExecutable>c:/Progra~1/PuTTY/plink.exe</sshExecutable>
>>> <scpExecutable>c:/Progra~1/PuTTY/pscp.exe</scpExecutable>
>>> </configuration>
>>> </server>
>>>
>>> But when I try this, I get the following error:
>>>
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error retrieving previous build number for artifact
>>> 'br.pucsp.apt:ereinion:jar': repository metadata for: 'snapshot
>>> br.pucsp.apt:ereinion:2.0.0-SNAPSHOT'
>>> could not be retrieved from repository: vulcano-repo due to an
>>> error: While
>>> configuring wagon for 'vulcano-repo': Unable to apply wagon
>>> configuration.
>>>
>>> Cannot find setter nor field in
>>> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for
>>> 'sshExecutable'
>>
>
> --
> View this message in context: http://www.nabble.com/What%27s-happened-to-wagon%27s-sshExecutable-setting--tp25372367p25384179.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: What's happened to wagon's sshExecutable setting?

2009-09-10T07:18:44Z

Great! Thanks for the tip. Is this documented somewhere I couldn't find?

Regards,
Daniel Serodio

brettporter wrote:

You need to use scpexe:// for the URL instead of scp://

- Brett

On 10/09/2009, at 6:09 AM, Daniel Serodio wrote:

>
> I'm on Windows XP, and I'm trying to make Maven deployment use my
> private key
> which is stored in PuTTY's Pageant ssh agent.
>
> I found an old recipe on the net that says I should use the following
> settings.xml:
>
> <server>
> <id>my-repo</id>
> <configuration>
> <sshExecutable>c:/Progra~1/PuTTY/plink.exe</sshExecutable>
> <scpExecutable>c:/Progra~1/PuTTY/pscp.exe</scpExecutable>
> </configuration>
> </server>
>
> But when I try this, I get the following error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error retrieving previous build number for artifact
> 'br.pucsp.apt:ereinion:jar': repository metadata for: 'snapshot
> br.pucsp.apt:ereinion:2.0.0-SNAPSHOT'
> could not be retrieved from repository: vulcano-repo due to an
> error: While
> configuring wagon for 'vulcano-repo': Unable to apply wagon
> configuration.
>
> Cannot find setter nor field in
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'

Re: What's happened to wagon's sshExecutable setting?

2009-09-09T20:43:53Z

You need to use scpexe:// for the URL instead of scp://

- Brett

On 10/09/2009, at 6:09 AM, Daniel Serodio wrote:

>
> I'm on Windows XP, and I'm trying to make Maven deployment use my
> private key
> which is stored in PuTTY's Pageant ssh agent.
>
> I found an old recipe on the net that says I should use the following
> settings.xml:
>
> <server>
> <id>my-repo</id>
> <configuration>
> <sshExecutable>c:/Progra~1/PuTTY/plink.exe</sshExecutable>
> <scpExecutable>c:/Progra~1/PuTTY/pscp.exe</scpExecutable>
> </configuration>
> </server>
>
> But when I try this, I get the following error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error retrieving previous build number for artifact
> 'br.pucsp.apt:ereinion:jar': repository metadata for: 'snapshot
> br.pucsp.apt:ereinion:2.0.0-SNAPSHOT'
> could not be retrieved from repository: vulcano-repo due to an
> error: While
> configuring wagon for 'vulcano-repo': Unable to apply wagon
> configuration.
>
> Cannot find setter nor field in
> org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'
> --
> View this message in context: http://www.nabble.com/What%27s-happened-to-wagon%27s-sshExecutable-setting--tp25372367p25372367.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

What's happened to wagon's sshExecutable setting?

2009-09-09T13:09:46Z

I'm on Windows XP, and I'm trying to make Maven deployment use my private key which is stored in PuTTY's Pageant ssh agent.

I found an old recipe on the net that says I should use the following settings.xml:

<server>
<id>my-repo</id>
<configuration>
<sshExecutable>c:/Progra~1/PuTTY/plink.exe</sshExecutable>
<scpExecutable>c:/Progra~1/PuTTY/pscp.exe</scpExecutable>
</configuration>
</server>

But when I try this, I get the following error:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error retrieving previous build number for artifact 'br.pucsp.apt:ereinion:jar': repository metadata for: 'snapshot br.pucsp.apt:ereinion:2.0.0-SNAPSHOT'
could not be retrieved from repository: vulcano-repo due to an error: While configuring wagon for 'vulcano-repo': Unable to apply wagon configuration.

Cannot find setter nor field in org.apache.maven.wagon.providers.ssh.jsch.ScpWagon for 'sshExecutable'

Re: wagon-scm: 409 when trying to deploy

2009-09-04T19:22:17Z

Try using v 1.0 of the SCM libraries in the extensions to match the
Wagon.

- Brett

On 05/09/2009, at 1:12 AM, droidin.net wrote:

>
> Thanks Brett,
>
> I changed deploy URL to:
> <snapshotRepository>
> <uniqueVersion>false</uniqueVersion>
> <id>engtools_snapshots</id>
> <name>EngTools Maven Repository</name>
>
> <url>scm:svn:http://continuum.td.foo.com/svn_repos/maven/snapshots</
> url>
> </snapshotRepository>
>
> and now I get buncj of linkage errors (I cleared everything
> including local
> maven repo)
>
> [INFO] [install:install {execution: default-install}]
> [INFO] Installing C:\foo\sources\PTE\pte-web\target\pte-web-1.0-
> SNAPSHOT.jar
> to C:\Documents an
> d
> Settings\boo\.m2\repository\foo\engtools\pte\pte-web\1.0-SNAPSHOT
> \pte-web-1.0-SNAPSHOT.j
> ar
> [INFO] [deploy:deploy {execution: default-deploy}]
> [INFO] Retrieving previous build number from engtools_snapshots
> [FATAL ERROR] org.apache.maven.plugin.deploy.DeployMojo#execute()
> caused a
> linkage error (java.lang.
> AbstractMethodError) and may be out-of-date. Check the realms:
> [FATAL ERROR] Plugin realm =
> app0.child-container[org.apache.maven.plugins:maven-deploy-plugin:2.4]
> urls[0] = file:/C:/Documents and
> Settings/boo/.m2/repository/org/apache/maven/plugins/maven-dep
> loy-plugin/2.4/maven-deploy-plugin-2.4.jar
> urls[1] = file:/C:/Documents and
> Settings/boo/.m2/repository/org/codehaus/plexus/plexus-utils/1
> .1/plexus-utils-1.1.jar
> [FATAL ERROR] Container realm = plexus.core
> urls[0] = file:/C:/java/apache-maven-2.2.0/bin/../lib/maven-2.2.0-
> uber.jar
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> org
> .apache
> .maven
> .scm
> .command
> .checkout.AbstractCheckOutCommand.executeCheckOutCommand(Lorg/apa
> che/maven/scm/provider/ScmProviderRepository;Lorg/apache/maven/scm/
> ScmFileSet;Lorg/apache/maven/scm/
> ScmVersion;)Lorg/apache/maven/scm/command/checkout/CheckOutScmResult;
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.AbstractMethodError:
> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.execute
> CheckOutCommand(Lorg/apache/maven/scm/provider/
> ScmProviderRepository;Lorg/apache/maven/scm/ScmFileSe
> t;Lorg/apache/maven/scm/ScmVersion;)Lorg/apache/maven/scm/command/
> checkout/CheckOutScmResult;
> at
> org
> .apache
> .maven
> .scm
> .command.checkout.AbstractCheckOutCommand.executeCommand(AbstractChec
> kOutCommand.java:49)
> at
> org
> .apache
> .maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
> at
> org
> .apache
> .maven
> .scm
> .provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmPro
> vider.java:354)
>
> brettporter wrote:
>>
>> You are trying to deploy directly to the SVN repository which won't
>> work unless it as auto_version turned on (and then you will get lots
>> of revisions).
>>
>> You probably need to change the URL to scm:svn:http:// instead of
>> just
>> http://
>>
>> - Brett
>>
>> On 26/08/2009, at 8:20 AM, droidin.net wrote:
>>
>>>
>>> When running "mvn deploy" I end up with error below (sorry for the
>>> long
>>> stacktrace). Just to mention - I had the same 409 error when using
>>> wagon-svn
>>> from http://is.gd/2yton. Any suggestions?
>>>
>>> I have Pom with the following settings for wagon-scm
>>>
>>> <build>
>>> <extensions>
>>> <extension>
>>> <groupId>org.apache.maven.wagon</groupId>
>>> <artifactId>wagon-scm</artifactId>
>>> <version>1.0-beta-6</version>
>>> </extension>
>>> <extension>
>>> <groupId>org.apache.maven.scm</groupId>
>>> <artifactId>maven-scm-manager-plexus</artifactId>
>>> <version>1.3-SNAPSHOT</version>
>>> </extension>
>>> <extension>
>>> <groupId>org.apache.maven.scm</groupId>
>>> <artifactId>maven-scm-provider-svnexe</artifactId>
>>> <version>1.3-SNAPSHOT</version>
>>> </extension>
>>> </extensions>
>>> </build>
>>>
>>> My settings.xml for the server I'm trying to deploy to
>>>
>>> <server>
>>> <id>engtools_snapshot</id>
>>> <username>rs1860xx</username>
>>> <password>mystrongpassword</password>
>>> <filePermissions>664</filePermissions>
>>> <directoryPermissions>775</directoryPermissions>
>>> </server>
>>>
>>>
>>> And the error:
>>>
>>> [DEBUG] Failed to transfer file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>> org.apache.maven.wagon.TransferFailedException: Failed to transfer
>>> file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>> at
>>> org
>>> .apache
>>> .maven
>>> .wagon
>>> .shared
>>> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .wagon
>>> .shared
>>> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
>>> 262)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:
>>> 172)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .deployer
>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>> 173)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
>>> 483)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoals(DefaultLifecycleExecutor.java:
>>> 678)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
>>> 519)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeTaskSegments(DefaultLifecycleExecutor.java:332)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> at
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
>>> 41)
>>> 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:597)
>>> 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)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error deploying artifact: Failed to transfer file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [DEBUG] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>> deploying
>>> artifact: Failed to transfer file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoals(DefaultLifecycleExecutor.java:
>>> 703)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
>>> 519)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeTaskSegments(DefaultLifecycleExecutor.java:332)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>>> at
>>> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
>>> 41)
>>> 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:597)
>>> 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: Failed to transfer file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>> 195)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
>>> 483)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .lifecycle
>>> .DefaultLifecycleExecutor
>>> .executeGoals(DefaultLifecycleExecutor.java:
>>> 678)
>>> ... 17 more
>>> Caused by:
>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>> Error deploying artifact: Failed to transfer file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .deployer
>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>> 173)
>>> ... 19 more
>>> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
>>> transfer file:
>>> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
>>> .
>>> Return code is: 409
>>> at
>>> org
>>> .apache
>>> .maven
>>> .wagon
>>> .shared
>>> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .wagon
>>> .shared
>>> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
>>> 262)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:
>>> 172)
>>> at
>>> org
>>> .apache
>>> .maven
>>> .artifact
>>> .deployer
>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
>>> ... 20 more
>>> --
>>> View this message in context:
>>> http://www.nabble.com/wagon-scm%3A-409-when-trying-to-deploy-tp25143236p25143236.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>> For additional commands, e-mail: wagon-users-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>> For additional commands, e-mail: wagon-users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/wagon-scm%3A-409-when-trying-to-deploy-tp25143236p25296238.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: wagon-scm: 409 when trying to deploy

2009-09-04T08:12:35Z

Thanks Brett,

I changed deploy URL to:
<snapshotRepository>
<uniqueVersion>false</uniqueVersion>
<id>engtools_snapshots</id>
<name>EngTools Maven Repository</name>
<url>scm:svn:http://continuum.td.foo.com/svn_repos/maven/snapshots</url>
</snapshotRepository>

and now I get buncj of linkage errors (I cleared everything including local maven repo)

[INFO] [install:install {execution: default-install}]
[INFO] Installing C:\foo\sources\PTE\pte-web\target\pte-web-1.0-SNAPSHOT.jar to C:\Documents an
d Settings\boo\.m2\repository\foo\engtools\pte\pte-web\1.0-SNAPSHOT\pte-web-1.0-SNAPSHOT.j
ar
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from engtools_snapshots
[FATAL ERROR] org.apache.maven.plugin.deploy.DeployMojo#execute() caused a linkage error (java.lang.
AbstractMethodError) and may be out-of-date. Check the realms:
[FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven-deploy-plugin:2.4]
urls[0] = file:/C:/Documents and Settings/boo/.m2/repository/org/apache/maven/plugins/maven-dep
loy-plugin/2.4/maven-deploy-plugin-2.4.jar
urls[1] = file:/C:/Documents and Settings/boo/.m2/repository/org/codehaus/plexus/plexus-utils/1
.1/plexus-utils-1.1.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/C:/java/apache-maven-2.2.0/bin/../lib/maven-2.2.0-uber.jar
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCheckOutCommand(Lorg/apa
che/maven/scm/provider/ScmProviderRepository;Lorg/apache/maven/scm/ScmFileSet;Lorg/apache/maven/scm/
ScmVersion;)Lorg/apache/maven/scm/command/checkout/CheckOutScmResult;
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.AbstractMethodError: org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.execute
CheckOutCommand(Lorg/apache/maven/scm/provider/ScmProviderRepository;Lorg/apache/maven/scm/ScmFileSe
t;Lorg/apache/maven/scm/ScmVersion;)Lorg/apache/maven/scm/command/checkout/CheckOutScmResult;
at org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractChec
kOutCommand.java:49)
at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
at org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.executeCommand(AbstractSvnScmPro
vider.java:354)

brettporter wrote:

You are trying to deploy directly to the SVN repository which won't
work unless it as auto_version turned on (and then you will get lots
of revisions).

You probably need to change the URL to scm:svn:http:// instead of just
http://

- Brett

On 26/08/2009, at 8:20 AM, droidin.net wrote:

>
> When running "mvn deploy" I end up with error below (sorry for the
> long
> stacktrace). Just to mention - I had the same 409 error when using
> wagon-svn
> from http://is.gd/2yton. Any suggestions?
>
> I have Pom with the following settings for wagon-scm
>
> <build>
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-scm</artifactId>
> <version>1.0-beta-6</version>
> </extension>
> <extension>
> <groupId>org.apache.maven.scm</groupId>
> <artifactId>maven-scm-manager-plexus</artifactId>
> <version>1.3-SNAPSHOT</version>
> </extension>
> <extension>
> <groupId>org.apache.maven.scm</groupId>
> <artifactId>maven-scm-provider-svnexe</artifactId>
> <version>1.3-SNAPSHOT</version>
> </extension>
> </extensions>
> </build>
>
> My settings.xml for the server I'm trying to deploy to
>
> <server>
> <id>engtools_snapshot</id>
> <username>rs1860xx</username>
> <password>mystrongpassword</password>
> <filePermissions>664</filePermissions>
> <directoryPermissions>775</directoryPermissions>
> </server>
>
>
> And the error:
>
> [DEBUG] Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> org.apache.maven.wagon.TransferFailedException: Failed to transfer
> file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
> 262)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
> at
> org
> .apache
> .maven
> .artifact
> .deployer
> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
> at
> org
> .apache
> .maven
> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
> 483)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 678)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
> 519)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
> 41)
> 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:597)
> 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)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
>
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> deploying
> artifact: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 703)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
> 519)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
> 41)
> 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:597)
> 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: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:195)
> at
> org
> .apache
> .maven
> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
> 483)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 678)
> ... 17 more
> Caused by:
> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> Error deploying artifact: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .artifact
> .deployer
> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
> ... 19 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
> transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
> 262)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
> at
> org
> .apache
> .maven
> .artifact
> .deployer
> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
> ... 20 more
> --
> View this message in context: http://www.nabble.com/wagon-scm%3A-409-when-trying-to-deploy-tp25143236p25143236.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
> For additional commands, e-mail: wagon-users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
For additional commands, e-mail: wagon-users-help@maven.apache.org

Re: wagon-scm: 409 when trying to deploy

2009-09-03T22:26:19Z

You are trying to deploy directly to the SVN repository which won't
work unless it as auto_version turned on (and then you will get lots
of revisions).

You probably need to change the URL to scm:svn:http:// instead of just
http://

- Brett

On 26/08/2009, at 8:20 AM, droidin.net wrote:

>
> When running "mvn deploy" I end up with error below (sorry for the
> long
> stacktrace). Just to mention - I had the same 409 error when using
> wagon-svn
> from http://is.gd/2yton. Any suggestions?
>
> I have Pom with the following settings for wagon-scm
>
> <build>
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-scm</artifactId>
> <version>1.0-beta-6</version>
> </extension>
> <extension>
> <groupId>org.apache.maven.scm</groupId>
> <artifactId>maven-scm-manager-plexus</artifactId>
> <version>1.3-SNAPSHOT</version>
> </extension>
> <extension>
> <groupId>org.apache.maven.scm</groupId>
> <artifactId>maven-scm-provider-svnexe</artifactId>
> <version>1.3-SNAPSHOT</version>
> </extension>
> </extensions>
> </build>
>
> My settings.xml for the server I'm trying to deploy to
>
> <server>
> <id>engtools_snapshot</id>
> <username>rs1860xx</username>
> <password>mystrongpassword</password>
> <filePermissions>664</filePermissions>
> <directoryPermissions>775</directoryPermissions>
> </server>
>
>
> And the error:
>
> [DEBUG] Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> org.apache.maven.wagon.TransferFailedException: Failed to transfer
> file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
> 262)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
> at
> org
> .apache
> .maven
> .artifact
> .deployer
> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
> at
> org
> .apache
> .maven
> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
> 483)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 678)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
> 519)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
> 41)
> 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:597)
> 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)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
>
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> deploying
> artifact: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 703)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
> 519)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor
> .executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:
> 41)
> 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:597)
> 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: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:195)
> at
> org
> .apache
> .maven
> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
> 483)
> at
> org
> .apache
> .maven
> .lifecycle
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 678)
> ... 17 more
> Caused by:
> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> Error deploying artifact: Failed to transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .artifact
> .deployer
> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
> at
> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
> ... 19 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Failed to
> transfer file:
> http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar
> .
> Return code is: 409
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
> at
> org
> .apache
> .maven
> .wagon
> .shared
> .http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
> 262)
> at
> org
> .apache
> .maven
> .artifact
> .manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
> at
> org
> .apache
> .maven
> .artifact
> .deployer
> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
> ... 20 more
> --
> View this message in context: http://www.nabble.com/wagon-scm%3A-409-when-trying-to-deploy-tp25143236p25143236.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: wagon-scm: 409 when trying to deploy

2009-08-27T12:00:47Z

Anybody, please? Any ideas?

droidin.net wrote:

When running "mvn deploy" I end up with error below (sorry for the long stacktrace). Just to mention - I had the same 409 error when using wagon-svn from http://is.gd/2yton. Any suggestions?

I have Pom with the following settings for wagon-scm

<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-scm</artifactId>
<version>1.0-beta-6</version>
</extension>
<extension>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-manager-plexus</artifactId>
<version>1.3-SNAPSHOT</version>
</extension>
<extension>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-svnexe</artifactId>
<version>1.3-SNAPSHOT</version>
</extension>
</extensions>
</build>

My settings.xml for the server I'm trying to deploy to

<server>
<id>engtools_snapshot</id>
<username>rs1860xx</username>
<password>mystrongpassword</password>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>

And the error:

[DEBUG] Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:262)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
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:597)
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)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409

[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
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:597)
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: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:195)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
... 17 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
... 19 more
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:262)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
... 20 more

wagon-scm: 409 when trying to deploy

2009-08-25T15:20:11Z

When running "mvn deploy" I end up with error below (sorry for the long stacktrace). Just to mention - I had the same 409 error when using wagon-svn from http://is.gd/2yton. Any suggestions?

I have Pom with the following settings for wagon-scm

<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-scm</artifactId>
<version>1.0-beta-6</version>
</extension>
<extension>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-manager-plexus</artifactId>
<version>1.3-SNAPSHOT</version>
</extension>
<extension>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-svnexe</artifactId>
<version>1.3-SNAPSHOT</version>
</extension>
</extensions>
</build>

My settings.xml for the server I'm trying to deploy to

<server>
<id>engtools_snapshot</id>
<username>rs1860xx</username>
<password>mystrongpassword</password>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>

And the error:

[DEBUG] Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:262)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
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:597)
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)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409

[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
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:597)
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: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:195)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
... 17 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:121)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
... 19 more
Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar. Return code is: 409
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:368)
at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:280)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:262)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
... 20 more

Disable host key checking in wagon-ssh provider

2009-06-25T09:23:15Z

I need to disable host key checking for wagon-ssh provider....how I can disable it ??

I notice that the provider get the value (ask, yes or no) from method AbstractKnownHostsProvider# getHostKeyChecking(), but I cannot understand how to set this property.

Thank you for the help,

Claudio

.........not everything that counts can be counted

Re: LigthweightHttpWagon resets system proxy properties

2009-05-15T18:48:37Z

They should be set on connection and unset on disconnection to try and
minimise problems when reused.

At what point is it being used without being set?

On 15/05/2009, at 11:25 PM, <henrik.sorensen@...> <henrik.sorensen@...
> wrote:

> Hi There,
>
> Using Maven 2.1, I found that some fishy is going on in
> LightweightHttpWagon.java.
>
> I carefully traced the setting and resetting of the http.proxy
> system properties from within the method openConnection. To my
> surprise the system properties were set to empty, so a resulting
> request for data failed.
>
> Has somebody else expirienced similar effects ?
>
> thanks for your help
> Henrik Sorensen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

LigthweightHttpWagon resets system proxy properties

2009-05-15T06:25:22Z

Hi There,

Using Maven 2.1, I found that some fishy is going on in LightweightHttpWagon.java.

I carefully traced the setting and resetting of the http.proxy system properties from within the method openConnection. To my surprise the system properties were set to empty, so a resulting request for data failed.

Has somebody else expirienced similar effects ?

thanks for your help
Henrik Sorensen

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-15T13:09:50Z

It should only be using an identity file based on a <privateKey> entry
in one of your settings.xml files - you might check that also.

On 16/04/2009, at 12:06 AM, CharlieCollins wrote:

>
>
> I don't have that identity file, no. My command line usage does not
> use that
> identity file. I am using host based authentication. My client has
> ~/.ssh/config with correct HostBasedAuthentication entries, and the
> server
> has HostBasedAuthentication yes, etc.
>
> If the scpexe command is passing switches to try to pass that file,
> that
> would be the problem. The identity file is not there, and doesn't
> need to be
> there, for host based authentication.
>
> I will download the source and attempt to get the plugin to reveal
> the exact
> scpexe command it is using. That will help me diagnose.
>
> Maven version is 2.1.0 (have tried with 2.0.9 and 2.1.0).
>
>
> brettporter wrote:
>>
>> At the surface it seems a permission issue with id_rsa, does you're
>> command line usage point to the same identity file as you've
>> configured in the settings for that server?
>>
>> What version of Maven is this? Maven 2.1.0 should be better at
>> logging
>> the command in debug mode, for example.
>>
>> - Brett
>>
>> On 15/04/2009, at 9:36 PM, CharlieCollins wrote:
>>
>>>
>>> Yes, scpexe also had problems. From my original note:
>>>
>>> "SCPEXE failure:
>>> [DEBUG] Configuring mojo
>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>> [DEBUG] (f) attachedArtifacts = []
>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>> scpexe://helios/intranet/maven2/reposnap
>>> [DEBUG] (s) localRepository = [local] ->
>>> file:///home/cruise/.m2/repository
>>> [DEBUG] (f) packaging = jar
>>> [DEBUG] (f) pomFile =
>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/
>>> pom.xml
>>> [DEBUG] (f) updateReleaseInfo = false
>>> [DEBUG] -- end configuration --
>>> [INFO] [deploy:deploy]
>>> altDeploymentRepository = null
>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>> Uploading:
>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/
>>> 0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity
>>> file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/
>>> axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied "
>>>
>>> If I could tell what command exactly it was trying to perform I
>>> might be
>>> able to troubleshoot it further, but I haven't yet gotten to the
>>> point of
>>> downloading the code and poking around myself.
>>> Scp and SSH from the command line, outside of Maven (as the same
>>> user), work
>>> fine.
>>>
>>>
>>>
>>> brettporter wrote:
>>>>
>>>> however ssh-external should support anything the command line does,
>>>> so
>>>> switching scp:// to scpexe:// should work. Based on your subject it
>>>> seems like you might have tried that - did it have problems?
>>>>
>>>> On 15/04/2009, at 4:41 AM, CharlieCollins wrote:
>>>>
>>>>>
>>>>>
>>>>> Thanks for the info, will do.
>>>>>
>>>>>
>>>>> Dan Tran wrote:
>>>>>>
>>>>>> ah, wagon-ssh does not support your host base authentication.
>>>>>> File a
>>>>>> JIRA and may be come up with a patch.
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
>>>>>> <charlie.collins@...> wrote:
>>>>>>>
>>>>>>> I don't think that's correct at all. I AM the "cruise" user
>>>>>>> (yes,
>>>>>>> when
>>>>>>> running Maven I am also running as the cruise user). Also, as
>>>>>>> stated,
>>>>>>> there
>>>>>>> is a /home/cruise/.ssh directory. It doesn't contain an
>>>>>>> "id_rsa"
>>>>>>> file,
>>>>>>> no,
>>>>>>> but it doesn't need to for host based auth. I can run "ssh
>>>>>>> helios"
>>>>>>> (helios
>>>>>>> being the remote machine I need to get into) OUTSIDE OF MAVEN
>>>>>>> just
>>>>>>> fine
>>>>>>> as
>>>>>>> the cruise user (as also previously stated).
>>>>>>>
>>>>>>> Once again, is host based authentication SUPPOSED to work,
>>>>>>> regardless of
>>>>>>> my
>>>>>>> setup?
>>>>>>>
>>>>>>> Maybe I need to set some configuration options, but the lack of
>>>>>>> documentation for what those might be hinders that a bit (at
>>>>>>> least I
>>>>>>> can't
>>>>>>> find docs - pointers appreciated).
>>>>>>>
>>>>>>>
>>>>>>> Dan Tran wrote:
>>>>>>>>
>>>>>>>> scp thinks you are 'cruise' user which you dont have access
>>>>>>>> it's
>>>>>>>> home/.ssh directory
>>>>>>>>
>>>>>>>> -D
>>>>>>>>
>>>>>>>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>>>>>>>> <charlie.collins@...> wrote:
>>>>>>>>>
>>>>>>>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>>>>>>>
>>>>>>>>> I can't find any examples or docs about host based auth
>>>>>>>>> either.
>>>>>>>>> Is host
>>>>>>>>> based auth supposed to work/supported?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Dan Tran wrote:
>>>>>>>>>>
>>>>>>>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>>>>>>>
>>>>>>>>>> -D
>>>>>>>>>>
>>>>>>>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>>>>>>>> <charlie.collins@...> wrote:
>>>>>>>>>>> I am not able to transfer files over SCP from a user/machine
>>>>>>>>>>> setup
>>>>>>>>>>> that is using host based authentication (note I am not
>>>>>>>>>>> talking
>>>>>>>>>>> about
>>>>>>>>>>> the host authentication can't be verified yes/no known_hosts
>>>>>>>>>>> issue,
>>>>>>>>>>> that's different - I am using host based authentication
>>>>>>>>>>> itself, not
>>>>>>>>>>> password, not certificate).
>>>>>>>>>>>
>>>>>>>>>>> Is host based auth supposed to work? Looks like Jsch
>>>>>>>>>>> supports
>>>>>>>>>>> it
>>>>>>>>>>> from
>>>>>>>>>>> the examples, but do any of the Wagon providers support it?
>>>>>>>>>>>
>>>>>>>>>>> From the client machine where Maven is running, to the
>>>>>>>>>>> server
>>>>>>>>>>> where I
>>>>>>>>>>> want to transfer files, using the same user account Maven is
>>>>>>>>>>> running
>>>>>>>>>>> as, works fine (outside of Maven):
>>>>>>>>>>>
>>>>>>>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>>>>>>>> cruise
>>>>>>>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>>>>>>>> Last login: Wed Apr 1 10:10:02 2009 from
>>>>>>>>>>> reddog.axiomainc.com
>>>>>>>>>>> cruise@helios:~$
>>>>>>>>>>>
>>>>>>>>>>> Inside of Maven, using the Deploy Plugin (which depends on
>>>>>>>>>>> Wagon), I
>>>>>>>>>>> get failures using either "scp" or "scpexe" in my
>>>>>>>>>>> distributionManagement section (which as I understand it
>>>>>>>>>>> switches
>>>>>>>>>>> between ssh and ssh external Wagon providers).
>>>>>>>>>>>
>>>>>>>>>>> POM has distributionManagement set, I have tried with an
>>>>>>>>>>> without
>>>>>>>>>>> settings.xml server sections (beyond user/pass most of the
>>>>>>>>>>> "configuration" elements for the providers appear
>>>>>>>>>>> undocumented, or at
>>>>>>>>>>> least I couldn't find it, so I am not sure if there is a
>>>>>>>>>>> config that
>>>>>>>>>>> might help).
>>>>>>>>>>>
>>>>>>>>>>> POM snippet (changed back and forth from scp to scpexe for
>>>>>>>>>>> various
>>>>>>>>>>> attempts):
>>>>>>>>>>> <distributionManagement>
>>>>>>>>>>> <repository>
>>>>>>>>>>> <uniqueVersion>false</uniqueVersion>
>>>>>>>>>>> <id>axioma-maven2</id>
>>>>>>>>>>> <name>Axioma Maven 2 Repository</name>
>>>>>>>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>>>>>>>> </repository>
>>>>>>>>>>> <snapshotRepository>
>>>>>>>>>>> <uniqueVersion>true</uniqueVersion>
>>>>>>>>>>> <id>axioma-maven2snap</id>
>>>>>>>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>>>>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>>>>>>>> </snapshotRepository>
>>>>>>>>>>> </distributionManagement>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> SCP failure:
>>>>>>>>>>> [DEBUG] Configuring mojo
>>>>>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy'
>>>>>>>>>>> -->
>>>>>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>>>>>> SNAPSHOT
>>>>>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>>>>>> scp://helios/intranet/maven2/reposnap
>>>>>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>>>>>> file:///home/cruise/.m2/repository
>>>>>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>>>>>> [DEBUG] (f) pomFile =
>>>>>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>>>>>> trunk/pom.xml
>>>>>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>>>>>> [DEBUG] -- end configuration --
>>>>>>>>>>> [INFO] [deploy:deploy]
>>>>>>>>>>> altDeploymentRepository = null
>>>>>>>>>>> [INFO] Retrieving previous build number from axioma-
>>>>>>>>>>> maven2snap
>>>>>>>>>>> The authenticity of host 'helios' can't be established.
>>>>>>>>>>> RSA key fingerprint is
>>>>>>>>>>> 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>>>>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>>>>>>>
>>>>>>>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts,
>>>>>>>>>>> but it
>>>>>>>>>>> shouldn't even be trying to use that, ~/.ssh/config also
>>>>>>>>>>> exists and
>>>>>>>>>>> lays out the host based authentication which works perfectly
>>>>>>>>>>> with no
>>>>>>>>>>> prompts outside of maven.)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> SCPEXE failure:
>>>>>>>>>>> [DEBUG] Configuring mojo
>>>>>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy'
>>>>>>>>>>> -->
>>>>>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>>>>>> SNAPSHOT
>>>>>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>>>>>> file:///home/cruise/.m2/repository
>>>>>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>>>>>> [DEBUG] (f) pomFile =
>>>>>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>>>>>> trunk/pom.xml
>>>>>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>>>>>> [DEBUG] -- end configuration --
>>>>>>>>>>> [INFO] [deploy:deploy]
>>>>>>>>>>> altDeploymentRepository = null
>>>>>>>>>>> [INFO] Retrieving previous build number from axioma-
>>>>>>>>>>> maven2snap
>>>>>>>>>>> Uploading:
>>>>>>>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/
>>>>>>>>>>> axioma-
>>>>>>>>>>> model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [ERROR] BUILD ERROR
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning:
>>>>>>>>>>> Identity
>>>>>>>>>>> file
>>>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>>>> directory.
>>>>>>>>>>> scp:
>>>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>>>> Permission denied
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [DEBUG] Trace
>>>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException:
>>>>>>>>>>> Error
>>>>>>>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>>>> directory.
>>>>>>>>>>> scp:
>>>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>>>> Permission denied
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:583)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .executeGoal(DefaultLifecycleExecutor.java:478)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:
>>>>>>>>>>> 330)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
>>>>>>>>>>> 336)
>>>>>>>>>>> at
>>>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:
>>>>>>>>>>> 287)
>>>>>>>>>>> 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:597)
>>>>>>>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>>>> directory.
>>>>>>>>>>> scp:
>>>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>>>> Permission denied
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>>>>>> 174)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .plugin
>>>>>>>>>>> .DefaultPluginManager.executeMojo(DefaultPluginManager.java:
>>>>>>>>>>> 451)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .lifecycle
>>>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>>>> ... 16 more
>>>>>>>>>>> Caused by:
>>>>>>>>>>> org
>>>>>>>>>>> .apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>>>>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity
>>>>>>>>>>> file
>>>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>>>> directory.
>>>>>>>>>>> scp:
>>>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>>>> Permission denied
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .artifact
>>>>>>>>>>> .deployer
>>>>>>>>>>> .DefaultArtifactDeployer
>>>>>>>>>>> .deploy(DefaultArtifactDeployer.java:
>>>>>>>>>>> 94)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>>>>>> 162)
>>>>>>>>>>> ... 18 more
>>>>>>>>>>> Caused by: org.apache.maven.wagon.TransferFailedException:
>>>>>>>>>>> Exit code:
>>>>>>>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not
>>>>>>>>>>> accessible:
>>>>>>>>>>> No
>>>>>>>>>>> such file or directory.
>>>>>>>>>>> scp:
>>>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>>>> Permission denied
>>>>>>>>>>>
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .wagon
>>>>>>>>>>> .providers
>>>>>>>>>>> .ssh
>>>>>>>>>>> .external
>>>>>>>>>>> .ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:
>>>>>>>>>>> 236)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .wagon
>>>>>>>>>>> .providers
>>>>>>>>>>> .ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:
>>>>>>>>>>> 295)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .artifact
>>>>>>>>>>> .manager
>>>>>>>>>>> .DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
>>>>>>>>>>> 244)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .artifact
>>>>>>>>>>> .manager
>>>>>>>>>>> .DefaultWagonManager.putArtifact(DefaultWagonManager.java:
>>>>>>>>>>> 160)
>>>>>>>>>>> at
>>>>>>>>>>> org
>>>>>>>>>>> .apache
>>>>>>>>>>> .maven
>>>>>>>>>>> .artifact
>>>>>>>>>>> .deployer
>>>>>>>>>>> .DefaultArtifactDeployer
>>>>>>>>>>> .deploy(DefaultArtifactDeployer.java:
>>>>>>>>>>> 80)
>>>>>>>>>>> ... 19 more
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>> [INFO] Total time: 26 seconds
>>>>>>>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>>>>>>>> [INFO] Final Memory: 22M/81M
>>>>>>>>>>> [INFO]
>>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Any ideas, help, etc. I have fought with this for half a
>>>>>>>>>>> day
>>>>>>>>>>> now and
>>>>>>>>>>> can't come up with anything. I can get other means of
>>>>>>>>>>> auth to
>>>>>>>>>>> work
>>>>>>>>>>> (after jumping through some hoops and getting much deeper
>>>>>>>>>>> into
>>>>>>>>>>> this
>>>>>>>>>>> than I ever wanted to be), password, cert, but they aren't
>>>>>>>>>>> supported
>>>>>>>>>>> where I work so those won't be allowed.
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> wagon-users-help@...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: wagon-users-
>>>>>>>>>> unsubscribe@...
>>>>>>>>>> For additional commands, e-mail: wagon-users-
>>>>>>>>>> help@...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> View this message in context:
>>>>>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>>>>>>>> Sent from the Wagon - Users mailing list archive at
>>>>>>>>> Nabble.com.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: wagon-users-
>>>>>>>> unsubscribe@...
>>>>>>>> For additional commands, e-mail: wagon-users-
>>>>>>>> help@...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
>>>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>> For additional commands, e-mail: wagon-users-
>>>>>> help@...
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23045511.html
>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>> For additional commands, e-mail: wagon-users-help@...
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23057239.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>> For additional commands, e-mail: wagon-users-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>> For additional commands, e-mail: wagon-users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23059685.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-15T07:06:18Z

I don't have that identity file, no. My command line usage does not use that identity file. I am using host based authentication. My client has ~/.ssh/config with correct HostBasedAuthentication entries, and the server has HostBasedAuthentication yes, etc.

If the scpexe command is passing switches to try to pass that file, that would be the problem. The identity file is not there, and doesn't need to be there, for host based authentication.

I will download the source and attempt to get the plugin to reveal the exact scpexe command it is using. That will help me diagnose.

Maven version is 2.1.0 (have tried with 2.0.9 and 2.1.0).

brettporter wrote:

At the surface it seems a permission issue with id_rsa, does you're
command line usage point to the same identity file as you've
configured in the settings for that server?

What version of Maven is this? Maven 2.1.0 should be better at logging
the command in debug mode, for example.

- Brett

On 15/04/2009, at 9:36 PM, CharlieCollins wrote:

>
> Yes, scpexe also had problems. From my original note:
>
> "SCPEXE failure:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
> scpexe://helios/intranet/maven2/reposnap
> [DEBUG] (s) localRepository = [local] ->
> file:///home/cruise/.m2/repository
> [DEBUG] (f) packaging = jar
> [DEBUG] (f) pomFile =
> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/
> pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from axioma-maven2snap
> Uploading:
> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/
> 0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp:
> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/
> axioma-model-0.5-20090401.144722-2.jar:
> Permission denied "
>
> If I could tell what command exactly it was trying to perform I
> might be
> able to troubleshoot it further, but I haven't yet gotten to the
> point of
> downloading the code and poking around myself.
> Scp and SSH from the command line, outside of Maven (as the same
> user), work
> fine.
>
>
>
> brettporter wrote:
>>
>> however ssh-external should support anything the command line does,
>> so
>> switching scp:// to scpexe:// should work. Based on your subject it
>> seems like you might have tried that - did it have problems?
>>
>> On 15/04/2009, at 4:41 AM, CharlieCollins wrote:
>>
>>>
>>>
>>> Thanks for the info, will do.
>>>
>>>
>>> Dan Tran wrote:
>>>>
>>>> ah, wagon-ssh does not support your host base authentication.
>>>> File a
>>>> JIRA and may be come up with a patch.
>>>>
>>>> -D
>>>>
>>>> On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
>>>> <charlie.collins@gmail.com> wrote:
>>>>>
>>>>> I don't think that's correct at all. I AM the "cruise" user (yes,
>>>>> when
>>>>> running Maven I am also running as the cruise user). Also, as
>>>>> stated,
>>>>> there
>>>>> is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa"
>>>>> file,
>>>>> no,
>>>>> but it doesn't need to for host based auth. I can run "ssh helios"
>>>>> (helios
>>>>> being the remote machine I need to get into) OUTSIDE OF MAVEN just
>>>>> fine
>>>>> as
>>>>> the cruise user (as also previously stated).
>>>>>
>>>>> Once again, is host based authentication SUPPOSED to work,
>>>>> regardless of
>>>>> my
>>>>> setup?
>>>>>
>>>>> Maybe I need to set some configuration options, but the lack of
>>>>> documentation for what those might be hinders that a bit (at
>>>>> least I
>>>>> can't
>>>>> find docs - pointers appreciated).
>>>>>
>>>>>
>>>>> Dan Tran wrote:
>>>>>>
>>>>>> scp thinks you are 'cruise' user which you dont have access it's
>>>>>> home/.ssh directory
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>>>>>> <charlie.collins@gmail.com> wrote:
>>>>>>>
>>>>>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>>>>>
>>>>>>> I can't find any examples or docs about host based auth either.
>>>>>>> Is host
>>>>>>> based auth supposed to work/supported?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Dan Tran wrote:
>>>>>>>>
>>>>>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>>>>>
>>>>>>>> -D
>>>>>>>>
>>>>>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>>>>>> <charlie.collins@gmail.com> wrote:
>>>>>>>>> I am not able to transfer files over SCP from a user/machine
>>>>>>>>> setup
>>>>>>>>> that is using host based authentication (note I am not talking
>>>>>>>>> about
>>>>>>>>> the host authentication can't be verified yes/no known_hosts
>>>>>>>>> issue,
>>>>>>>>> that's different - I am using host based authentication
>>>>>>>>> itself, not
>>>>>>>>> password, not certificate).
>>>>>>>>>
>>>>>>>>> Is host based auth supposed to work? Looks like Jsch supports
>>>>>>>>> it
>>>>>>>>> from
>>>>>>>>> the examples, but do any of the Wagon providers support it?
>>>>>>>>>
>>>>>>>>> From the client machine where Maven is running, to the server
>>>>>>>>> where I
>>>>>>>>> want to transfer files, using the same user account Maven is
>>>>>>>>> running
>>>>>>>>> as, works fine (outside of Maven):
>>>>>>>>>
>>>>>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>>>>>> cruise
>>>>>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>>>>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>>>>>>>> cruise@helios:~$
>>>>>>>>>
>>>>>>>>> Inside of Maven, using the Deploy Plugin (which depends on
>>>>>>>>> Wagon), I
>>>>>>>>> get failures using either "scp" or "scpexe" in my
>>>>>>>>> distributionManagement section (which as I understand it
>>>>>>>>> switches
>>>>>>>>> between ssh and ssh external Wagon providers).
>>>>>>>>>
>>>>>>>>> POM has distributionManagement set, I have tried with an
>>>>>>>>> without
>>>>>>>>> settings.xml server sections (beyond user/pass most of the
>>>>>>>>> "configuration" elements for the providers appear
>>>>>>>>> undocumented, or at
>>>>>>>>> least I couldn't find it, so I am not sure if there is a
>>>>>>>>> config that
>>>>>>>>> might help).
>>>>>>>>>
>>>>>>>>> POM snippet (changed back and forth from scp to scpexe for
>>>>>>>>> various
>>>>>>>>> attempts):
>>>>>>>>> <distributionManagement>
>>>>>>>>> <repository>
>>>>>>>>> <uniqueVersion>false</uniqueVersion>
>>>>>>>>> <id>axioma-maven2</id>
>>>>>>>>> <name>Axioma Maven 2 Repository</name>
>>>>>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>>>>>> </repository>
>>>>>>>>> <snapshotRepository>
>>>>>>>>> <uniqueVersion>true</uniqueVersion>
>>>>>>>>> <id>axioma-maven2snap</id>
>>>>>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>>>>>> </snapshotRepository>
>>>>>>>>> </distributionManagement>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> SCP failure:
>>>>>>>>> [DEBUG] Configuring mojo
>>>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>>>> SNAPSHOT
>>>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>>>> scp://helios/intranet/maven2/reposnap
>>>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>>>> file:///home/cruise/.m2/repository
>>>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>>>> [DEBUG] (f) pomFile =
>>>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>>>> trunk/pom.xml
>>>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>>>> [DEBUG] -- end configuration --
>>>>>>>>> [INFO] [deploy:deploy]
>>>>>>>>> altDeploymentRepository = null
>>>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>>>> The authenticity of host 'helios' can't be established.
>>>>>>>>> RSA key fingerprint is
>>>>>>>>> 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>>>>>
>>>>>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts,
>>>>>>>>> but it
>>>>>>>>> shouldn't even be trying to use that, ~/.ssh/config also
>>>>>>>>> exists and
>>>>>>>>> lays out the host based authentication which works perfectly
>>>>>>>>> with no
>>>>>>>>> prompts outside of maven.)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> SCPEXE failure:
>>>>>>>>> [DEBUG] Configuring mojo
>>>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>>>> SNAPSHOT
>>>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>>>> file:///home/cruise/.m2/repository
>>>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>>>> [DEBUG] (f) pomFile =
>>>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>>>> trunk/pom.xml
>>>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>>>> [DEBUG] -- end configuration --
>>>>>>>>> [INFO] [deploy:deploy]
>>>>>>>>> altDeploymentRepository = null
>>>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>>>> Uploading:
>>>>>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-
>>>>>>>>> model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [ERROR] BUILD ERROR
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning:
>>>>>>>>> Identity
>>>>>>>>> file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [DEBUG] Trace
>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>>>>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:583)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoal(DefaultLifecycleExecutor.java:478)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:
>>>>>>>>> 330)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>> at
>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>> at
>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>> 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:597)
>>>>>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>>>> 174)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .plugin
>>>>>>>>> .DefaultPluginManager.executeMojo(DefaultPluginManager.java:
>>>>>>>>> 451)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>> ... 16 more
>>>>>>>>> Caused by:
>>>>>>>>> org
>>>>>>>>> .apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity
>>>>>>>>> file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .deployer
>>>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:
>>>>>>>>> 94)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>>>> 162)
>>>>>>>>> ... 18 more
>>>>>>>>> Caused by: org.apache.maven.wagon.TransferFailedException:
>>>>>>>>> Exit code:
>>>>>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not
>>>>>>>>> accessible:
>>>>>>>>> No
>>>>>>>>> such file or directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .wagon
>>>>>>>>> .providers
>>>>>>>>> .ssh
>>>>>>>>> .external
>>>>>>>>> .ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .wagon
>>>>>>>>> .providers
>>>>>>>>> .ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .manager
>>>>>>>>> .DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
>>>>>>>>> 244)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .manager
>>>>>>>>> .DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .deployer
>>>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:
>>>>>>>>> 80)
>>>>>>>>> ... 19 more
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Total time: 26 seconds
>>>>>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>>>>>> [INFO] Final Memory: 22M/81M
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Any ideas, help, etc. I have fought with this for half a day
>>>>>>>>> now and
>>>>>>>>> can't come up with anything. I can get other means of auth to
>>>>>>>>> work
>>>>>>>>> (after jumping through some hoops and getting much deeper into
>>>>>>>>> this
>>>>>>>>> than I ever wanted to be), password, cert, but they aren't
>>>>>>>>> supported
>>>>>>>>> where I work so those won't be allowed.
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>>>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: wagon-users-
>>>>>>>> unsubscribe@maven.apache.org
>>>>>>>> For additional commands, e-mail: wagon-users-
>>>>>>>> help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: wagon-users-
>>>>>> help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23045511.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23057239.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
> For additional commands, e-mail: wagon-users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
For additional commands, e-mail: wagon-users-help@maven.apache.org

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-15T04:57:55Z

At the surface it seems a permission issue with id_rsa, does you're
command line usage point to the same identity file as you've
configured in the settings for that server?

What version of Maven is this? Maven 2.1.0 should be better at logging
the command in debug mode, for example.

- Brett

On 15/04/2009, at 9:36 PM, CharlieCollins wrote:

>
> Yes, scpexe also had problems. From my original note:
>
> "SCPEXE failure:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
> scpexe://helios/intranet/maven2/reposnap
> [DEBUG] (s) localRepository = [local] ->
> file:///home/cruise/.m2/repository
> [DEBUG] (f) packaging = jar
> [DEBUG] (f) pomFile =
> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/
> pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from axioma-maven2snap
> Uploading:
> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/
> 0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp:
> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/
> axioma-model-0.5-20090401.144722-2.jar:
> Permission denied "
>
> If I could tell what command exactly it was trying to perform I
> might be
> able to troubleshoot it further, but I haven't yet gotten to the
> point of
> downloading the code and poking around myself.
> Scp and SSH from the command line, outside of Maven (as the same
> user), work
> fine.
>
>
>
> brettporter wrote:
>>
>> however ssh-external should support anything the command line does,
>> so
>> switching scp:// to scpexe:// should work. Based on your subject it
>> seems like you might have tried that - did it have problems?
>>
>> On 15/04/2009, at 4:41 AM, CharlieCollins wrote:
>>
>>>
>>>
>>> Thanks for the info, will do.
>>>
>>>
>>> Dan Tran wrote:
>>>>
>>>> ah, wagon-ssh does not support your host base authentication.
>>>> File a
>>>> JIRA and may be come up with a patch.
>>>>
>>>> -D
>>>>
>>>> On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
>>>> <charlie.collins@...> wrote:
>>>>>
>>>>> I don't think that's correct at all. I AM the "cruise" user (yes,
>>>>> when
>>>>> running Maven I am also running as the cruise user). Also, as
>>>>> stated,
>>>>> there
>>>>> is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa"
>>>>> file,
>>>>> no,
>>>>> but it doesn't need to for host based auth. I can run "ssh helios"
>>>>> (helios
>>>>> being the remote machine I need to get into) OUTSIDE OF MAVEN just
>>>>> fine
>>>>> as
>>>>> the cruise user (as also previously stated).
>>>>>
>>>>> Once again, is host based authentication SUPPOSED to work,
>>>>> regardless of
>>>>> my
>>>>> setup?
>>>>>
>>>>> Maybe I need to set some configuration options, but the lack of
>>>>> documentation for what those might be hinders that a bit (at
>>>>> least I
>>>>> can't
>>>>> find docs - pointers appreciated).
>>>>>
>>>>>
>>>>> Dan Tran wrote:
>>>>>>
>>>>>> scp thinks you are 'cruise' user which you dont have access it's
>>>>>> home/.ssh directory
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>>>>>> <charlie.collins@...> wrote:
>>>>>>>
>>>>>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>>>>>
>>>>>>> I can't find any examples or docs about host based auth either.
>>>>>>> Is host
>>>>>>> based auth supposed to work/supported?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Dan Tran wrote:
>>>>>>>>
>>>>>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>>>>>
>>>>>>>> -D
>>>>>>>>
>>>>>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>>>>>> <charlie.collins@...> wrote:
>>>>>>>>> I am not able to transfer files over SCP from a user/machine
>>>>>>>>> setup
>>>>>>>>> that is using host based authentication (note I am not talking
>>>>>>>>> about
>>>>>>>>> the host authentication can't be verified yes/no known_hosts
>>>>>>>>> issue,
>>>>>>>>> that's different - I am using host based authentication
>>>>>>>>> itself, not
>>>>>>>>> password, not certificate).
>>>>>>>>>
>>>>>>>>> Is host based auth supposed to work? Looks like Jsch supports
>>>>>>>>> it
>>>>>>>>> from
>>>>>>>>> the examples, but do any of the Wagon providers support it?
>>>>>>>>>
>>>>>>>>> From the client machine where Maven is running, to the server
>>>>>>>>> where I
>>>>>>>>> want to transfer files, using the same user account Maven is
>>>>>>>>> running
>>>>>>>>> as, works fine (outside of Maven):
>>>>>>>>>
>>>>>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>>>>>> cruise
>>>>>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>>>>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>>>>>>>> cruise@helios:~$
>>>>>>>>>
>>>>>>>>> Inside of Maven, using the Deploy Plugin (which depends on
>>>>>>>>> Wagon), I
>>>>>>>>> get failures using either "scp" or "scpexe" in my
>>>>>>>>> distributionManagement section (which as I understand it
>>>>>>>>> switches
>>>>>>>>> between ssh and ssh external Wagon providers).
>>>>>>>>>
>>>>>>>>> POM has distributionManagement set, I have tried with an
>>>>>>>>> without
>>>>>>>>> settings.xml server sections (beyond user/pass most of the
>>>>>>>>> "configuration" elements for the providers appear
>>>>>>>>> undocumented, or at
>>>>>>>>> least I couldn't find it, so I am not sure if there is a
>>>>>>>>> config that
>>>>>>>>> might help).
>>>>>>>>>
>>>>>>>>> POM snippet (changed back and forth from scp to scpexe for
>>>>>>>>> various
>>>>>>>>> attempts):
>>>>>>>>> <distributionManagement>
>>>>>>>>> <repository>
>>>>>>>>> <uniqueVersion>false</uniqueVersion>
>>>>>>>>> <id>axioma-maven2</id>
>>>>>>>>> <name>Axioma Maven 2 Repository</name>
>>>>>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>>>>>> </repository>
>>>>>>>>> <snapshotRepository>
>>>>>>>>> <uniqueVersion>true</uniqueVersion>
>>>>>>>>> <id>axioma-maven2snap</id>
>>>>>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>>>>>> </snapshotRepository>
>>>>>>>>> </distributionManagement>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> SCP failure:
>>>>>>>>> [DEBUG] Configuring mojo
>>>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>>>> SNAPSHOT
>>>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>>>> scp://helios/intranet/maven2/reposnap
>>>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>>>> file:///home/cruise/.m2/repository
>>>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>>>> [DEBUG] (f) pomFile =
>>>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>>>> trunk/pom.xml
>>>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>>>> [DEBUG] -- end configuration --
>>>>>>>>> [INFO] [deploy:deploy]
>>>>>>>>> altDeploymentRepository = null
>>>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>>>> The authenticity of host 'helios' can't be established.
>>>>>>>>> RSA key fingerprint is
>>>>>>>>> 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>>>>>
>>>>>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts,
>>>>>>>>> but it
>>>>>>>>> shouldn't even be trying to use that, ~/.ssh/config also
>>>>>>>>> exists and
>>>>>>>>> lays out the host based authentication which works perfectly
>>>>>>>>> with no
>>>>>>>>> prompts outside of maven.)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> SCPEXE failure:
>>>>>>>>> [DEBUG] Configuring mojo
>>>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>>>> SNAPSHOT
>>>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>>>> file:///home/cruise/.m2/repository
>>>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>>>> [DEBUG] (f) pomFile =
>>>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>>>> trunk/pom.xml
>>>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>>>> [DEBUG] -- end configuration --
>>>>>>>>> [INFO] [deploy:deploy]
>>>>>>>>> altDeploymentRepository = null
>>>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>>>> Uploading:
>>>>>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-
>>>>>>>>> model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [ERROR] BUILD ERROR
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning:
>>>>>>>>> Identity
>>>>>>>>> file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [DEBUG] Trace
>>>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>>>>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:583)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoal(DefaultLifecycleExecutor.java:478)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:
>>>>>>>>> 330)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .execute(DefaultLifecycleExecutor.java:142)
>>>>>>>>> at
>>>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>>>> at
>>>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>>>> 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:597)
>>>>>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>>>> 174)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .plugin
>>>>>>>>> .DefaultPluginManager.executeMojo(DefaultPluginManager.java:
>>>>>>>>> 451)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .lifecycle
>>>>>>>>> .DefaultLifecycleExecutor
>>>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>>>> ... 16 more
>>>>>>>>> Caused by:
>>>>>>>>> org
>>>>>>>>> .apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity
>>>>>>>>> file
>>>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>>>> directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .deployer
>>>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:
>>>>>>>>> 94)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>>>> 162)
>>>>>>>>> ... 18 more
>>>>>>>>> Caused by: org.apache.maven.wagon.TransferFailedException:
>>>>>>>>> Exit code:
>>>>>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not
>>>>>>>>> accessible:
>>>>>>>>> No
>>>>>>>>> such file or directory.
>>>>>>>>> scp:
>>>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>>>> Permission denied
>>>>>>>>>
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .wagon
>>>>>>>>> .providers
>>>>>>>>> .ssh
>>>>>>>>> .external
>>>>>>>>> .ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .wagon
>>>>>>>>> .providers
>>>>>>>>> .ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .manager
>>>>>>>>> .DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:
>>>>>>>>> 244)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .manager
>>>>>>>>> .DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>>>>>>>> at
>>>>>>>>> org
>>>>>>>>> .apache
>>>>>>>>> .maven
>>>>>>>>> .artifact
>>>>>>>>> .deployer
>>>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:
>>>>>>>>> 80)
>>>>>>>>> ... 19 more
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>> [INFO] Total time: 26 seconds
>>>>>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>>>>>> [INFO] Final Memory: 22M/81M
>>>>>>>>> [INFO]
>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Any ideas, help, etc. I have fought with this for half a day
>>>>>>>>> now and
>>>>>>>>> can't come up with anything. I can get other means of auth to
>>>>>>>>> work
>>>>>>>>> (after jumping through some hoops and getting much deeper into
>>>>>>>>> this
>>>>>>>>> than I ever wanted to be), password, cert, but they aren't
>>>>>>>>> supported
>>>>>>>>> where I work so those won't be allowed.
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: wagon-users-
>>>>>>>> unsubscribe@...
>>>>>>>> For additional commands, e-mail: wagon-users-
>>>>>>>> help@...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> View this message in context:
>>>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>> For additional commands, e-mail: wagon-users-
>>>>>> help@...
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>> For additional commands, e-mail: wagon-users-help@...
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23045511.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>> For additional commands, e-mail: wagon-users-help@...
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>> For additional commands, e-mail: wagon-users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23057239.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-15T04:36:20Z

Yes, scpexe also had problems. From my original note:

"SCPEXE failure:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
[DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
scpexe://helios/intranet/maven2/reposnap
[DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
/opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from axioma-maven2snap
Uploading: scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
/home/cruise/.ssh/id_rsa not accessible: No such file or directory.
scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
Permission denied "

If I could tell what command exactly it was trying to perform I might be able to troubleshoot it further, but I haven't yet gotten to the point of downloading the code and poking around myself.
Scp and SSH from the command line, outside of Maven (as the same user), work fine.

brettporter wrote:

however ssh-external should support anything the command line does, so
switching scp:// to scpexe:// should work. Based on your subject it
seems like you might have tried that - did it have problems?

On 15/04/2009, at 4:41 AM, CharlieCollins wrote:

>
>
> Thanks for the info, will do.
>
>
> Dan Tran wrote:
>>
>> ah, wagon-ssh does not support your host base authentication. File a
>> JIRA and may be come up with a patch.
>>
>> -D
>>
>> On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
>> <charlie.collins@gmail.com> wrote:
>>>
>>> I don't think that's correct at all. I AM the "cruise" user (yes,
>>> when
>>> running Maven I am also running as the cruise user). Also, as
>>> stated,
>>> there
>>> is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa"
>>> file,
>>> no,
>>> but it doesn't need to for host based auth. I can run "ssh helios"
>>> (helios
>>> being the remote machine I need to get into) OUTSIDE OF MAVEN just
>>> fine
>>> as
>>> the cruise user (as also previously stated).
>>>
>>> Once again, is host based authentication SUPPOSED to work,
>>> regardless of
>>> my
>>> setup?
>>>
>>> Maybe I need to set some configuration options, but the lack of
>>> documentation for what those might be hinders that a bit (at least I
>>> can't
>>> find docs - pointers appreciated).
>>>
>>>
>>> Dan Tran wrote:
>>>>
>>>> scp thinks you are 'cruise' user which you dont have access it's
>>>> home/.ssh directory
>>>>
>>>> -D
>>>>
>>>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>>>> <charlie.collins@gmail.com> wrote:
>>>>>
>>>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>>>
>>>>> I can't find any examples or docs about host based auth either.
>>>>> Is host
>>>>> based auth supposed to work/supported?
>>>>>
>>>>>
>>>>>
>>>>> Dan Tran wrote:
>>>>>>
>>>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>>>> <charlie.collins@gmail.com> wrote:
>>>>>>> I am not able to transfer files over SCP from a user/machine
>>>>>>> setup
>>>>>>> that is using host based authentication (note I am not talking
>>>>>>> about
>>>>>>> the host authentication can't be verified yes/no known_hosts
>>>>>>> issue,
>>>>>>> that's different - I am using host based authentication
>>>>>>> itself, not
>>>>>>> password, not certificate).
>>>>>>>
>>>>>>> Is host based auth supposed to work? Looks like Jsch supports
>>>>>>> it
>>>>>>> from
>>>>>>> the examples, but do any of the Wagon providers support it?
>>>>>>>
>>>>>>> From the client machine where Maven is running, to the server
>>>>>>> where I
>>>>>>> want to transfer files, using the same user account Maven is
>>>>>>> running
>>>>>>> as, works fine (outside of Maven):
>>>>>>>
>>>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>>>> cruise
>>>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>>>>>> cruise@helios:~$
>>>>>>>
>>>>>>> Inside of Maven, using the Deploy Plugin (which depends on
>>>>>>> Wagon), I
>>>>>>> get failures using either "scp" or "scpexe" in my
>>>>>>> distributionManagement section (which as I understand it
>>>>>>> switches
>>>>>>> between ssh and ssh external Wagon providers).
>>>>>>>
>>>>>>> POM has distributionManagement set, I have tried with an without
>>>>>>> settings.xml server sections (beyond user/pass most of the
>>>>>>> "configuration" elements for the providers appear
>>>>>>> undocumented, or at
>>>>>>> least I couldn't find it, so I am not sure if there is a
>>>>>>> config that
>>>>>>> might help).
>>>>>>>
>>>>>>> POM snippet (changed back and forth from scp to scpexe for
>>>>>>> various
>>>>>>> attempts):
>>>>>>> <distributionManagement>
>>>>>>> <repository>
>>>>>>> <uniqueVersion>false</uniqueVersion>
>>>>>>> <id>axioma-maven2</id>
>>>>>>> <name>Axioma Maven 2 Repository</name>
>>>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>>>> </repository>
>>>>>>> <snapshotRepository>
>>>>>>> <uniqueVersion>true</uniqueVersion>
>>>>>>> <id>axioma-maven2snap</id>
>>>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>>>> </snapshotRepository>
>>>>>>> </distributionManagement>
>>>>>>>
>>>>>>>
>>>>>>> SCP failure:
>>>>>>> [DEBUG] Configuring mojo
>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>> SNAPSHOT
>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>> scp://helios/intranet/maven2/reposnap
>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>> file:///home/cruise/.m2/repository
>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>> [DEBUG] (f) pomFile =
>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>> trunk/pom.xml
>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>> [DEBUG] -- end configuration --
>>>>>>> [INFO] [deploy:deploy]
>>>>>>> altDeploymentRepository = null
>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>> The authenticity of host 'helios' can't be established.
>>>>>>> RSA key fingerprint is
>>>>>>> 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>>>
>>>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
>>>>>>> shouldn't even be trying to use that, ~/.ssh/config also
>>>>>>> exists and
>>>>>>> lays out the host based authentication which works perfectly
>>>>>>> with no
>>>>>>> prompts outside of maven.)
>>>>>>>
>>>>>>>
>>>>>>> SCPEXE failure:
>>>>>>> [DEBUG] Configuring mojo
>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>> SNAPSHOT
>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>> file:///home/cruise/.m2/repository
>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>> [DEBUG] (f) pomFile =
>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>> trunk/pom.xml
>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>> [DEBUG] -- end configuration --
>>>>>>> [INFO] [deploy:deploy]
>>>>>>> altDeploymentRepository = null
>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>> Uploading:
>>>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-
>>>>>>> model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [ERROR] BUILD ERROR
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning:
>>>>>>> Identity
>>>>>>> file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [DEBUG] Trace
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:583)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoal(DefaultLifecycleExecutor.java:478)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .execute(DefaultLifecycleExecutor.java:142)
>>>>>>> at
>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>> at
>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>> 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:597)
>>>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>> 174)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .plugin
>>>>>>> .DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>> ... 16 more
>>>>>>> Caused by:
>>>>>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .deployer
>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>> 162)
>>>>>>> ... 18 more
>>>>>>> Caused by: org.apache.maven.wagon.TransferFailedException:
>>>>>>> Exit code:
>>>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not
>>>>>>> accessible:
>>>>>>> No
>>>>>>> such file or directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .wagon
>>>>>>> .providers
>>>>>>> .ssh
>>>>>>> .external
>>>>>>> .ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .wagon
>>>>>>> .providers
>>>>>>> .ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .manager
>>>>>>> .DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .manager
>>>>>>> .DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .deployer
>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>>>>>>> ... 19 more
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Total time: 26 seconds
>>>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>>>> [INFO] Final Memory: 22M/81M
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> Any ideas, help, etc. I have fought with this for half a day
>>>>>>> now and
>>>>>>> can't come up with anything. I can get other means of auth to
>>>>>>> work
>>>>>>> (after jumping through some hoops and getting much deeper into
>>>>>>> this
>>>>>>> than I ever wanted to be), password, cert, but they aren't
>>>>>>> supported
>>>>>>> where I work so those won't be allowed.
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: wagon-users-
>>>>>> help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23045511.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
> For additional commands, e-mail: wagon-users-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
For additional commands, e-mail: wagon-users-help@maven.apache.org

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-14T17:17:52Z

however ssh-external should support anything the command line does, so
switching scp:// to scpexe:// should work. Based on your subject it
seems like you might have tried that - did it have problems?

On 15/04/2009, at 4:41 AM, CharlieCollins wrote:

>
>
> Thanks for the info, will do.
>
>
> Dan Tran wrote:
>>
>> ah, wagon-ssh does not support your host base authentication. File a
>> JIRA and may be come up with a patch.
>>
>> -D
>>
>> On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
>> <charlie.collins@...> wrote:
>>>
>>> I don't think that's correct at all. I AM the "cruise" user (yes,
>>> when
>>> running Maven I am also running as the cruise user). Also, as
>>> stated,
>>> there
>>> is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa"
>>> file,
>>> no,
>>> but it doesn't need to for host based auth. I can run "ssh helios"
>>> (helios
>>> being the remote machine I need to get into) OUTSIDE OF MAVEN just
>>> fine
>>> as
>>> the cruise user (as also previously stated).
>>>
>>> Once again, is host based authentication SUPPOSED to work,
>>> regardless of
>>> my
>>> setup?
>>>
>>> Maybe I need to set some configuration options, but the lack of
>>> documentation for what those might be hinders that a bit (at least I
>>> can't
>>> find docs - pointers appreciated).
>>>
>>>
>>> Dan Tran wrote:
>>>>
>>>> scp thinks you are 'cruise' user which you dont have access it's
>>>> home/.ssh directory
>>>>
>>>> -D
>>>>
>>>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>>>> <charlie.collins@...> wrote:
>>>>>
>>>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>>>
>>>>> I can't find any examples or docs about host based auth either.
>>>>> Is host
>>>>> based auth supposed to work/supported?
>>>>>
>>>>>
>>>>>
>>>>> Dan Tran wrote:
>>>>>>
>>>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>>>> <charlie.collins@...> wrote:
>>>>>>> I am not able to transfer files over SCP from a user/machine
>>>>>>> setup
>>>>>>> that is using host based authentication (note I am not talking
>>>>>>> about
>>>>>>> the host authentication can't be verified yes/no known_hosts
>>>>>>> issue,
>>>>>>> that's different - I am using host based authentication
>>>>>>> itself, not
>>>>>>> password, not certificate).
>>>>>>>
>>>>>>> Is host based auth supposed to work? Looks like Jsch supports
>>>>>>> it
>>>>>>> from
>>>>>>> the examples, but do any of the Wagon providers support it?
>>>>>>>
>>>>>>> From the client machine where Maven is running, to the server
>>>>>>> where I
>>>>>>> want to transfer files, using the same user account Maven is
>>>>>>> running
>>>>>>> as, works fine (outside of Maven):
>>>>>>>
>>>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>>>> cruise
>>>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>>>>>> cruise@helios:~$
>>>>>>>
>>>>>>> Inside of Maven, using the Deploy Plugin (which depends on
>>>>>>> Wagon), I
>>>>>>> get failures using either "scp" or "scpexe" in my
>>>>>>> distributionManagement section (which as I understand it
>>>>>>> switches
>>>>>>> between ssh and ssh external Wagon providers).
>>>>>>>
>>>>>>> POM has distributionManagement set, I have tried with an without
>>>>>>> settings.xml server sections (beyond user/pass most of the
>>>>>>> "configuration" elements for the providers appear
>>>>>>> undocumented, or at
>>>>>>> least I couldn't find it, so I am not sure if there is a
>>>>>>> config that
>>>>>>> might help).
>>>>>>>
>>>>>>> POM snippet (changed back and forth from scp to scpexe for
>>>>>>> various
>>>>>>> attempts):
>>>>>>> <distributionManagement>
>>>>>>> <repository>
>>>>>>> <uniqueVersion>false</uniqueVersion>
>>>>>>> <id>axioma-maven2</id>
>>>>>>> <name>Axioma Maven 2 Repository</name>
>>>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>>>> </repository>
>>>>>>> <snapshotRepository>
>>>>>>> <uniqueVersion>true</uniqueVersion>
>>>>>>> <id>axioma-maven2snap</id>
>>>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>>>> </snapshotRepository>
>>>>>>> </distributionManagement>
>>>>>>>
>>>>>>>
>>>>>>> SCP failure:
>>>>>>> [DEBUG] Configuring mojo
>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>> SNAPSHOT
>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>> scp://helios/intranet/maven2/reposnap
>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>> file:///home/cruise/.m2/repository
>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>> [DEBUG] (f) pomFile =
>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>> trunk/pom.xml
>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>> [DEBUG] -- end configuration --
>>>>>>> [INFO] [deploy:deploy]
>>>>>>> altDeploymentRepository = null
>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>> The authenticity of host 'helios' can't be established.
>>>>>>> RSA key fingerprint is
>>>>>>> 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>>>
>>>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
>>>>>>> shouldn't even be trying to use that, ~/.ssh/config also
>>>>>>> exists and
>>>>>>> lays out the host based authentication which works perfectly
>>>>>>> with no
>>>>>>> prompts outside of maven.)
>>>>>>>
>>>>>>>
>>>>>>> SCPEXE failure:
>>>>>>> [DEBUG] Configuring mojo
>>>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-
>>>>>>> SNAPSHOT
>>>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>>>> file:///home/cruise/.m2/repository
>>>>>>> [DEBUG] (f) packaging = jar
>>>>>>> [DEBUG] (f) pomFile =
>>>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/
>>>>>>> trunk/pom.xml
>>>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>>>> [DEBUG] -- end configuration --
>>>>>>> [INFO] [deploy:deploy]
>>>>>>> altDeploymentRepository = null
>>>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>>>> Uploading:
>>>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-
>>>>>>> model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [ERROR] BUILD ERROR
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning:
>>>>>>> Identity
>>>>>>> file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>>
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [DEBUG] Trace
>>>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:583)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoal(DefaultLifecycleExecutor.java:478)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .execute(DefaultLifecycleExecutor.java:142)
>>>>>>> at
>>>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>>>> at
>>>>>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>>>> 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:597)
>>>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>> 174)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .plugin
>>>>>>> .DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .lifecycle
>>>>>>> .DefaultLifecycleExecutor
>>>>>>> .executeGoals(DefaultLifecycleExecutor.java:558)
>>>>>>> ... 16 more
>>>>>>> Caused by:
>>>>>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity file
>>>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or
>>>>>>> directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .deployer
>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:
>>>>>>> 162)
>>>>>>> ... 18 more
>>>>>>> Caused by: org.apache.maven.wagon.TransferFailedException:
>>>>>>> Exit code:
>>>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not
>>>>>>> accessible:
>>>>>>> No
>>>>>>> such file or directory.
>>>>>>> scp:
>>>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-
>>>>>>> SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>>>> Permission denied
>>>>>>>
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .wagon
>>>>>>> .providers
>>>>>>> .ssh
>>>>>>> .external
>>>>>>> .ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .wagon
>>>>>>> .providers
>>>>>>> .ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .manager
>>>>>>> .DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .manager
>>>>>>> .DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>>>>>> at
>>>>>>> org
>>>>>>> .apache
>>>>>>> .maven
>>>>>>> .artifact
>>>>>>> .deployer
>>>>>>> .DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>>>>>>> ... 19 more
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Total time: 26 seconds
>>>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>>>> [INFO] Final Memory: 22M/81M
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>> Any ideas, help, etc. I have fought with this for half a day
>>>>>>> now and
>>>>>>> can't come up with anything. I can get other means of auth to
>>>>>>> work
>>>>>>> (after jumping through some hoops and getting much deeper into
>>>>>>> this
>>>>>>> than I ever wanted to be), password, cert, but they aren't
>>>>>>> supported
>>>>>>> where I work so those won't be allowed.
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>>> For additional commands, e-mail: wagon-users-
>>>>>> help@...
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>> For additional commands, e-mail: wagon-users-help@...
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>> For additional commands, e-mail: wagon-users-help@...
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>> For additional commands, e-mail: wagon-users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23045511.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: SSH External -o BatchMode yes

2009-04-14T17:14:21Z

On 14/04/2009, at 11:30 AM, Tim Riley wrote:

> I have run into a situation with the wagon-ssh-external version 1.0-
> beta-5
> and maven 2.1.0. Before I attempt to fix the problem myself I wanted
> to ask
> here if there is another solution.
>
> I'm currently using Reflection Secure IT, which requires all SSH -o
> options
> be placed in quotations unfortunately I cannot deviate from this
> technology.

One quick workaround might be to put an intervening script in between
maven and the PATH that corrects the problem, something like: http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/

> My other option and my prefered option is to
> submit a patch that gets rolled into the nightly build of the wagon
> provider.

This would be best - certainly submit the issue and patch to be rolled
in. Adding the quotes is not harmful to openssh, so I'd say it's ok to
add them for all cases.

I wouldn't recommend using a snapshot though - instead it's best if
you release the library internally (1.0-beta-5-MYCOMPANY-1) and use
that. This assumes you've set up your own repository and the builds
all use it.

Adding the following will then override the Maven one:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>1.0-beta-5-MYCOMPANY-1</version>
</extension>
</extensions>
</build>

Once the Wagon is formally released you can replace the version with
the new one.

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-14T11:41:36Z

Thanks for the info, will do.

Dan Tran wrote:

ah, wagon-ssh does not support your host base authentication. File a
JIRA and may be come up with a patch.

-D

On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
<charlie.collins@gmail.com> wrote:
>
> I don't think that's correct at all. I AM the "cruise" user (yes, when
> running Maven I am also running as the cruise user). Also, as stated, there
> is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa" file, no,
> but it doesn't need to for host based auth. I can run "ssh helios" (helios
> being the remote machine I need to get into) OUTSIDE OF MAVEN just fine as
> the cruise user (as also previously stated).
>
> Once again, is host based authentication SUPPOSED to work, regardless of my
> setup?
>
> Maybe I need to set some configuration options, but the lack of
> documentation for what those might be hinders that a bit (at least I can't
> find docs - pointers appreciated).
>
>
> Dan Tran wrote:
>>
>> scp thinks you are 'cruise' user which you dont have access it's
>> home/.ssh directory
>>
>> -D
>>
>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>> <charlie.collins@gmail.com> wrote:
>>>
>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>
>>> I can't find any examples or docs about host based auth either. Is host
>>> based auth supposed to work/supported?
>>>
>>>
>>>
>>> Dan Tran wrote:
>>>>
>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>
>>>> -D
>>>>
>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>> <charlie.collins@gmail.com> wrote:
>>>>> I am not able to transfer files over SCP from a user/machine setup
>>>>> that is using host based authentication (note I am not talking about
>>>>> the host authentication can't be verified yes/no known_hosts issue,
>>>>> that's different - I am using host based authentication itself, not
>>>>> password, not certificate).
>>>>>
>>>>> Is host based auth supposed to work? Looks like Jsch supports it from
>>>>> the examples, but do any of the Wagon providers support it?
>>>>>
>>>>> From the client machine where Maven is running, to the server where I
>>>>> want to transfer files, using the same user account Maven is running
>>>>> as, works fine (outside of Maven):
>>>>>
>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>> cruise
>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>>>> cruise@helios:~$
>>>>>
>>>>> Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
>>>>> get failures using either "scp" or "scpexe" in my
>>>>> distributionManagement section (which as I understand it switches
>>>>> between ssh and ssh external Wagon providers).
>>>>>
>>>>> POM has distributionManagement set, I have tried with an without
>>>>> settings.xml server sections (beyond user/pass most of the
>>>>> "configuration" elements for the providers appear undocumented, or at
>>>>> least I couldn't find it, so I am not sure if there is a config that
>>>>> might help).
>>>>>
>>>>> POM snippet (changed back and forth from scp to scpexe for various
>>>>> attempts):
>>>>> <distributionManagement>
>>>>> <repository>
>>>>> <uniqueVersion>false</uniqueVersion>
>>>>> <id>axioma-maven2</id>
>>>>> <name>Axioma Maven 2 Repository</name>
>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>> </repository>
>>>>> <snapshotRepository>
>>>>> <uniqueVersion>true</uniqueVersion>
>>>>> <id>axioma-maven2snap</id>
>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>> </snapshotRepository>
>>>>> </distributionManagement>
>>>>>
>>>>>
>>>>> SCP failure:
>>>>> [DEBUG] Configuring mojo
>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>> scp://helios/intranet/maven2/reposnap
>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>> file:///home/cruise/.m2/repository
>>>>> [DEBUG] (f) packaging = jar
>>>>> [DEBUG] (f) pomFile =
>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>> [DEBUG] -- end configuration --
>>>>> [INFO] [deploy:deploy]
>>>>> altDeploymentRepository = null
>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>> The authenticity of host 'helios' can't be established.
>>>>> RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>
>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
>>>>> shouldn't even be trying to use that, ~/.ssh/config also exists and
>>>>> lays out the host based authentication which works perfectly with no
>>>>> prompts outside of maven.)
>>>>>
>>>>>
>>>>> SCPEXE failure:
>>>>> [DEBUG] Configuring mojo
>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>> file:///home/cruise/.m2/repository
>>>>> [DEBUG] (f) packaging = jar
>>>>> [DEBUG] (f) pomFile =
>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>> [DEBUG] -- end configuration --
>>>>> [INFO] [deploy:deploy]
>>>>> altDeploymentRepository = null
>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>> Uploading:
>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [DEBUG] Trace
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>> 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:597)
>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
>>>>> at
>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>> ... 16 more
>>>>> Caused by:
>>>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>>>>> at
>>>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
>>>>> ... 18 more
>>>>> Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
>>>>> such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>>>> at
>>>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>>>> at
>>>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
>>>>> at
>>>>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>>>> at
>>>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>>>>> ... 19 more
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Total time: 26 seconds
>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>> [INFO] Final Memory: 22M/81M
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Any ideas, help, etc. I have fought with this for half a day now and
>>>>> can't come up with anything. I can get other means of auth to work
>>>>> (after jumping through some hoops and getting much deeper into this
>>>>> than I ever wanted to be), password, cert, but they aren't supported
>>>>> where I work so those won't be allowed.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
> For additional commands, e-mail: wagon-users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
For additional commands, e-mail: wagon-users-help@maven.apache.org

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-14T11:31:20Z

ah, wagon-ssh does not support your host base authentication. File a
JIRA and may be come up with a patch.

-D

On Tue, Apr 14, 2009 at 10:55 AM, CharlieCollins
<charlie.collins@...> wrote:

>
> I don't think that's correct at all. I AM the "cruise" user (yes, when
> running Maven I am also running as the cruise user). Also, as stated, there
> is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa" file, no,
> but it doesn't need to for host based auth. I can run "ssh helios" (helios
> being the remote machine I need to get into) OUTSIDE OF MAVEN just fine as
> the cruise user (as also previously stated).
>
> Once again, is host based authentication SUPPOSED to work, regardless of my
> setup?
>
> Maybe I need to set some configuration options, but the lack of
> documentation for what those might be hinders that a bit (at least I can't
> find docs - pointers appreciated).
>
>
> Dan Tran wrote:
>>
>> scp thinks you are 'cruise' user which you dont have access it's
>> home/.ssh directory
>>
>> -D
>>
>> On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
>> <charlie.collins@...> wrote:
>>>
>>> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>>>
>>> I can't find any examples or docs about host based auth either. Is host
>>> based auth supposed to work/supported?
>>>
>>>
>>>
>>> Dan Tran wrote:
>>>>
>>>> maven-2.1.0 has the latest wagon, see if it works for you.
>>>>
>>>> -D
>>>>
>>>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>>>> <charlie.collins@...> wrote:
>>>>> I am not able to transfer files over SCP from a user/machine setup
>>>>> that is using host based authentication (note I am not talking about
>>>>> the host authentication can't be verified yes/no known_hosts issue,
>>>>> that's different - I am using host based authentication itself, not
>>>>> password, not certificate).
>>>>>
>>>>> Is host based auth supposed to work? Looks like Jsch supports it from
>>>>> the examples, but do any of the Wagon providers support it?
>>>>>
>>>>> From the client machine where Maven is running, to the server where I
>>>>> want to transfer files, using the same user account Maven is running
>>>>> as, works fine (outside of Maven):
>>>>>
>>>>> cruise@reddog:/home/ccollins$ whoami
>>>>> cruise
>>>>> cruise@reddog:/home/ccollins$ ssh helios
>>>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>>>> cruise@helios:~$
>>>>>
>>>>> Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
>>>>> get failures using either "scp" or "scpexe" in my
>>>>> distributionManagement section (which as I understand it switches
>>>>> between ssh and ssh external Wagon providers).
>>>>>
>>>>> POM has distributionManagement set, I have tried with an without
>>>>> settings.xml server sections (beyond user/pass most of the
>>>>> "configuration" elements for the providers appear undocumented, or at
>>>>> least I couldn't find it, so I am not sure if there is a config that
>>>>> might help).
>>>>>
>>>>> POM snippet (changed back and forth from scp to scpexe for various
>>>>> attempts):
>>>>> <distributionManagement>
>>>>> <repository>
>>>>> <uniqueVersion>false</uniqueVersion>
>>>>> <id>axioma-maven2</id>
>>>>> <name>Axioma Maven 2 Repository</name>
>>>>> <url>scp://helios/intranet/maven2/repo</url>
>>>>> </repository>
>>>>> <snapshotRepository>
>>>>> <uniqueVersion>true</uniqueVersion>
>>>>> <id>axioma-maven2snap</id>
>>>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>>>> </snapshotRepository>
>>>>> </distributionManagement>
>>>>>
>>>>>
>>>>> SCP failure:
>>>>> [DEBUG] Configuring mojo
>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>> scp://helios/intranet/maven2/reposnap
>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>> file:///home/cruise/.m2/repository
>>>>> [DEBUG] (f) packaging = jar
>>>>> [DEBUG] (f) pomFile =
>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>> [DEBUG] -- end configuration --
>>>>> [INFO] [deploy:deploy]
>>>>> altDeploymentRepository = null
>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>> The authenticity of host 'helios' can't be established.
>>>>> RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>>>> Are you sure you want to continue connecting? (yes/no): yes
>>>>>
>>>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
>>>>> shouldn't even be trying to use that, ~/.ssh/config also exists and
>>>>> lays out the host based authentication which works perfectly with no
>>>>> prompts outside of maven.)
>>>>>
>>>>>
>>>>> SCPEXE failure:
>>>>> [DEBUG] Configuring mojo
>>>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>>>> [DEBUG] (f) attachedArtifacts = []
>>>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>>>> scpexe://helios/intranet/maven2/reposnap
>>>>> [DEBUG] (s) localRepository = [local] ->
>>>>> file:///home/cruise/.m2/repository
>>>>> [DEBUG] (f) packaging = jar
>>>>> [DEBUG] (f) pomFile =
>>>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>>>> [DEBUG] (f) updateReleaseInfo = false
>>>>> [DEBUG] -- end configuration --
>>>>> [INFO] [deploy:deploy]
>>>>> altDeploymentRepository = null
>>>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>>>> Uploading:
>>>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>>
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [DEBUG] Trace
>>>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>>>> at
>>>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>>>> 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:597)
>>>>> 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: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
>>>>> at
>>>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>>>> at
>>>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>>>> ... 16 more
>>>>> Caused by:
>>>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>>>> Error deploying artifact: Exit code: 1 - Warning: Identity file
>>>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>>>>> at
>>>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
>>>>> ... 18 more
>>>>> Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
>>>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
>>>>> such file or directory.
>>>>> scp:
>>>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>>>> Permission denied
>>>>>
>>>>> at
>>>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>>>> at
>>>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>>>> at
>>>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
>>>>> at
>>>>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>>>> at
>>>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>>>>> ... 19 more
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Total time: 26 seconds
>>>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>>>> [INFO] Final Memory: 22M/81M
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> Any ideas, help, etc. I have fought with this for half a day now and
>>>>> can't come up with anything. I can get other means of auth to work
>>>>> (after jumping through some hoops and getting much deeper into this
>>>>> than I ever wanted to be), password, cert, but they aren't supported
>>>>> where I work so those won't be allowed.
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>>> For additional commands, e-mail: wagon-users-help@...
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>>> For additional commands, e-mail: wagon-users-help@...
>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
>>> Sent from the Wagon - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>> For additional commands, e-mail: wagon-users-help@...
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>> For additional commands, e-mail: wagon-users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23044542.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-14T10:55:35Z

I don't think that's correct at all. I AM the "cruise" user (yes, when running Maven I am also running as the cruise user). Also, as stated, there is a /home/cruise/.ssh directory. It doesn't contain an "id_rsa" file, no, but it doesn't need to for host based auth. I can run "ssh helios" (helios being the remote machine I need to get into) OUTSIDE OF MAVEN just fine as the cruise user (as also previously stated).

Once again, is host based authentication SUPPOSED to work, regardless of my setup?

Maybe I need to set some configuration options, but the lack of documentation for what those might be hinders that a bit (at least I can't find docs - pointers appreciated).

Dan Tran wrote:

scp thinks you are 'cruise' user which you dont have access it's
home/.ssh directory

-D

On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
<charlie.collins@gmail.com> wrote:
>
> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>
> I can't find any examples or docs about host based auth either. Is host
> based auth supposed to work/supported?
>
>
>
> Dan Tran wrote:
>>
>> maven-2.1.0 has the latest wagon, see if it works for you.
>>
>> -D
>>
>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>> <charlie.collins@gmail.com> wrote:
>>> I am not able to transfer files over SCP from a user/machine setup
>>> that is using host based authentication (note I am not talking about
>>> the host authentication can't be verified yes/no known_hosts issue,
>>> that's different - I am using host based authentication itself, not
>>> password, not certificate).
>>>
>>> Is host based auth supposed to work? Looks like Jsch supports it from
>>> the examples, but do any of the Wagon providers support it?
>>>
>>> From the client machine where Maven is running, to the server where I
>>> want to transfer files, using the same user account Maven is running
>>> as, works fine (outside of Maven):
>>>
>>> cruise@reddog:/home/ccollins$ whoami
>>> cruise
>>> cruise@reddog:/home/ccollins$ ssh helios
>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>> cruise@helios:~$
>>>
>>> Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
>>> get failures using either "scp" or "scpexe" in my
>>> distributionManagement section (which as I understand it switches
>>> between ssh and ssh external Wagon providers).
>>>
>>> POM has distributionManagement set, I have tried with an without
>>> settings.xml server sections (beyond user/pass most of the
>>> "configuration" elements for the providers appear undocumented, or at
>>> least I couldn't find it, so I am not sure if there is a config that
>>> might help).
>>>
>>> POM snippet (changed back and forth from scp to scpexe for various
>>> attempts):
>>> <distributionManagement>
>>> <repository>
>>> <uniqueVersion>false</uniqueVersion>
>>> <id>axioma-maven2</id>
>>> <name>Axioma Maven 2 Repository</name>
>>> <url>scp://helios/intranet/maven2/repo</url>
>>> </repository>
>>> <snapshotRepository>
>>> <uniqueVersion>true</uniqueVersion>
>>> <id>axioma-maven2snap</id>
>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>> </snapshotRepository>
>>> </distributionManagement>
>>>
>>>
>>> SCP failure:
>>> [DEBUG] Configuring mojo
>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>> [DEBUG] (f) attachedArtifacts = []
>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>> scp://helios/intranet/maven2/reposnap
>>> [DEBUG] (s) localRepository = [local] ->
>>> file:///home/cruise/.m2/repository
>>> [DEBUG] (f) packaging = jar
>>> [DEBUG] (f) pomFile =
>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>> [DEBUG] (f) updateReleaseInfo = false
>>> [DEBUG] -- end configuration --
>>> [INFO] [deploy:deploy]
>>> altDeploymentRepository = null
>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>> The authenticity of host 'helios' can't be established.
>>> RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>> Are you sure you want to continue connecting? (yes/no): yes
>>>
>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
>>> shouldn't even be trying to use that, ~/.ssh/config also exists and
>>> lays out the host based authentication which works perfectly with no
>>> prompts outside of maven.)
>>>
>>>
>>> SCPEXE failure:
>>> [DEBUG] Configuring mojo
>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>> [DEBUG] (f) attachedArtifacts = []
>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>> scpexe://helios/intranet/maven2/reposnap
>>> [DEBUG] (s) localRepository = [local] ->
>>> file:///home/cruise/.m2/repository
>>> [DEBUG] (f) packaging = jar
>>> [DEBUG] (f) pomFile =
>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>> [DEBUG] (f) updateReleaseInfo = false
>>> [DEBUG] -- end configuration --
>>> [INFO] [deploy:deploy]
>>> altDeploymentRepository = null
>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>> Uploading:
>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [DEBUG] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> 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:597)
>>> 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: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> ... 16 more
>>> Caused by:
>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>> Error deploying artifact: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
>>> ... 18 more
>>> Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
>>> such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>> at
>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>> at
>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
>>> at
>>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>> at
>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>>> ... 19 more
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 26 seconds
>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>> [INFO] Final Memory: 22M/81M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Any ideas, help, etc. I have fought with this for half a day now and
>>> can't come up with anything. I can get other means of auth to work
>>> (after jumping through some hoops and getting much deeper into this
>>> than I ever wanted to be), password, cert, but they aren't supported
>>> where I work so those won't be allowed.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: wagon-users-help@maven.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
> For additional commands, e-mail: wagon-users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
For additional commands, e-mail: wagon-users-help@maven.apache.org

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-14T10:07:59Z

scp thinks you are 'cruise' user which you dont have access it's
home/.ssh directory

-D

On Tue, Apr 14, 2009 at 9:43 AM, CharlieCollins
<charlie.collins@...> wrote:

>
> I have tried with 2.0.9 and 2.1.0, neither seems to work.
>
> I can't find any examples or docs about host based auth either. Is host
> based auth supposed to work/supported?
>
>
>
> Dan Tran wrote:
>>
>> maven-2.1.0 has the latest wagon, see if it works for you.
>>
>> -D
>>
>> On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
>> <charlie.collins@...> wrote:
>>> I am not able to transfer files over SCP from a user/machine setup
>>> that is using host based authentication (note I am not talking about
>>> the host authentication can't be verified yes/no known_hosts issue,
>>> that's different - I am using host based authentication itself, not
>>> password, not certificate).
>>>
>>> Is host based auth supposed to work? Looks like Jsch supports it from
>>> the examples, but do any of the Wagon providers support it?
>>>
>>> From the client machine where Maven is running, to the server where I
>>> want to transfer files, using the same user account Maven is running
>>> as, works fine (outside of Maven):
>>>
>>> cruise@reddog:/home/ccollins$ whoami
>>> cruise
>>> cruise@reddog:/home/ccollins$ ssh helios
>>> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
>>> cruise@helios:~$
>>>
>>> Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
>>> get failures using either "scp" or "scpexe" in my
>>> distributionManagement section (which as I understand it switches
>>> between ssh and ssh external Wagon providers).
>>>
>>> POM has distributionManagement set, I have tried with an without
>>> settings.xml server sections (beyond user/pass most of the
>>> "configuration" elements for the providers appear undocumented, or at
>>> least I couldn't find it, so I am not sure if there is a config that
>>> might help).
>>>
>>> POM snippet (changed back and forth from scp to scpexe for various
>>> attempts):
>>> <distributionManagement>
>>> <repository>
>>> <uniqueVersion>false</uniqueVersion>
>>> <id>axioma-maven2</id>
>>> <name>Axioma Maven 2 Repository</name>
>>> <url>scp://helios/intranet/maven2/repo</url>
>>> </repository>
>>> <snapshotRepository>
>>> <uniqueVersion>true</uniqueVersion>
>>> <id>axioma-maven2snap</id>
>>> <name>Axioma Maven 2 Snapshot Repository</name>
>>> <url>scp://helios/intranet/maven2/reposnap</url>
>>> </snapshotRepository>
>>> </distributionManagement>
>>>
>>>
>>> SCP failure:
>>> [DEBUG] Configuring mojo
>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>> [DEBUG] (f) attachedArtifacts = []
>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>> scp://helios/intranet/maven2/reposnap
>>> [DEBUG] (s) localRepository = [local] ->
>>> file:///home/cruise/.m2/repository
>>> [DEBUG] (f) packaging = jar
>>> [DEBUG] (f) pomFile =
>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>> [DEBUG] (f) updateReleaseInfo = false
>>> [DEBUG] -- end configuration --
>>> [INFO] [deploy:deploy]
>>> altDeploymentRepository = null
>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>> The authenticity of host 'helios' can't be established.
>>> RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
>>> Are you sure you want to continue connecting? (yes/no): yes
>>>
>>> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
>>> shouldn't even be trying to use that, ~/.ssh/config also exists and
>>> lays out the host based authentication which works perfectly with no
>>> prompts outside of maven.)
>>>
>>>
>>> SCPEXE failure:
>>> [DEBUG] Configuring mojo
>>> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
>>> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
>>> [DEBUG] (f) attachedArtifacts = []
>>> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
>>> scpexe://helios/intranet/maven2/reposnap
>>> [DEBUG] (s) localRepository = [local] ->
>>> file:///home/cruise/.m2/repository
>>> [DEBUG] (f) packaging = jar
>>> [DEBUG] (f) pomFile =
>>> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
>>> [DEBUG] (f) updateReleaseInfo = false
>>> [DEBUG] -- end configuration --
>>> [INFO] [deploy:deploy]
>>> altDeploymentRepository = null
>>> [INFO] Retrieving previous build number from axioma-maven2snap
>>> Uploading:
>>> scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>>
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [DEBUG] Trace
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Error
>>> deploying artifact: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
>>> 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:597)
>>> 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: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
>>> at
>>> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
>>> at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
>>> ... 16 more
>>> Caused by:
>>> org.apache.maven.artifact.deployer.ArtifactDeploymentException:
>>> Error deploying artifact: Exit code: 1 - Warning: Identity file
>>> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
>>> at
>>> org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
>>> ... 18 more
>>> Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
>>> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
>>> such file or directory.
>>> scp:
>>> /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
>>> Permission denied
>>>
>>> at
>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
>>> at
>>> org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
>>> at
>>> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
>>> at
>>> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
>>> at
>>> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
>>> ... 19 more
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 26 seconds
>>> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
>>> [INFO] Final Memory: 22M/81M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>>
>>> Any ideas, help, etc. I have fought with this for half a day now and
>>> can't come up with anything. I can get other means of auth to work
>>> (after jumping through some hoops and getting much deeper into this
>>> than I ever wanted to be), password, cert, but they aren't supported
>>> where I work so those won't be allowed.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>>> For additional commands, e-mail: wagon-users-help@...
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wagon-users-unsubscribe@...
>> For additional commands, e-mail: wagon-users-help@...
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Using-Wagon-SSH-or-SSH-external-with-HOST-BASED-authenticaton--tp22829131p23043194.html
> Sent from the Wagon - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-14T09:43:10Z

I have tried with 2.0.9 and 2.1.0, neither seems to work.

I can't find any examples or docs about host based auth either. Is host based auth supposed to work/supported?

Dan Tran wrote:

maven-2.1.0 has the latest wagon, see if it works for you.

-D

On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
<charlie.collins@gmail.com> wrote:
> I am not able to transfer files over SCP from a user/machine setup
> that is using host based authentication (note I am not talking about
> the host authentication can't be verified yes/no known_hosts issue,
> that's different - I am using host based authentication itself, not
> password, not certificate).
>
> Is host based auth supposed to work? Looks like Jsch supports it from
> the examples, but do any of the Wagon providers support it?
>
> From the client machine where Maven is running, to the server where I
> want to transfer files, using the same user account Maven is running
> as, works fine (outside of Maven):
>
> cruise@reddog:/home/ccollins$ whoami
> cruise
> cruise@reddog:/home/ccollins$ ssh helios
> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
> cruise@helios:~$
>
> Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
> get failures using either "scp" or "scpexe" in my
> distributionManagement section (which as I understand it switches
> between ssh and ssh external Wagon providers).
>
> POM has distributionManagement set, I have tried with an without
> settings.xml server sections (beyond user/pass most of the
> "configuration" elements for the providers appear undocumented, or at
> least I couldn't find it, so I am not sure if there is a config that
> might help).
>
> POM snippet (changed back and forth from scp to scpexe for various attempts):
> <distributionManagement>
> <repository>
> <uniqueVersion>false</uniqueVersion>
> <id>axioma-maven2</id>
> <name>Axioma Maven 2 Repository</name>
> <url>scp://helios/intranet/maven2/repo</url>
> </repository>
> <snapshotRepository>
> <uniqueVersion>true</uniqueVersion>
> <id>axioma-maven2snap</id>
> <name>Axioma Maven 2 Snapshot Repository</name>
> <url>scp://helios/intranet/maven2/reposnap</url>
> </snapshotRepository>
> </distributionManagement>
>
>
> SCP failure:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
> scp://helios/intranet/maven2/reposnap
> [DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
> [DEBUG] (f) packaging = jar
> [DEBUG] (f) pomFile =
> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from axioma-maven2snap
> The authenticity of host 'helios' can't be established.
> RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
> Are you sure you want to continue connecting? (yes/no): yes
>
> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
> shouldn't even be trying to use that, ~/.ssh/config also exists and
> lays out the host based authentication which works perfectly with no
> prompts outside of maven.)
>
>
> SCPEXE failure:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
> scpexe://helios/intranet/maven2/reposnap
> [DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
> [DEBUG] (f) packaging = jar
> [DEBUG] (f) pomFile =
> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from axioma-maven2snap
> Uploading: scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
>
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:597)
> 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: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> Error deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
> ... 18 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
> such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
> at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
> ... 19 more
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26 seconds
> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
> [INFO] Final Memory: 22M/81M
> [INFO] ------------------------------------------------------------------------
>
>
> Any ideas, help, etc. I have fought with this for half a day now and
> can't come up with anything. I can get other means of auth to work
> (after jumping through some hoops and getting much deeper into this
> than I ever wanted to be), password, cert, but they aren't supported
> where I work so those won't be allowed.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
> For additional commands, e-mail: wagon-users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@maven.apache.org
For additional commands, e-mail: wagon-users-help@maven.apache.org

SSH External -o BatchMode yes

2009-04-13T18:30:59Z

I have run into a situation with the wagon-ssh-external version 1.0-beta-5
and maven 2.1.0. Before I attempt to fix the problem myself I wanted to ask
here if there is another solution.

I'm currently using Reflection Secure IT, which requires all SSH -o options
be placed in quotations unfortunately I cannot deviate from this technology.
The problem is that ScpExternalWagon.java places the BatchMode option as an
argument without quotes resulting in a failing SSH command. The way I see it
I can branch the code and attempt to add another wagon provider, but I have
yet to find decent documentation as how this is done (If you know of any
please forward it my way). My other option and my prefered option is to
submit a patch that gets rolled into the nightly build of the wagon
provider.

Line 251 of ScpExternalWagon.java
cl.createArgument().setValue( "BatchMode yes" );

Results in...
ssh -o BatchMode yes [REST OF COMMAND]

What I need is...
ssh -o "BatchMode yes" [REST OF COMMAND]

Any help would be much appreciated as this is a time critical issue for me
and the success of maven at my organization.

Sincerely,
Tim

How is necessary to make webdav works behind a proxy?

2009-04-03T07:49:46Z

Hello,

according to WAGON-82, it is possible to use webdav behind a proxy
starting with the fix version 1.0-beta-3. I tried to use maven-2.1.0
(which uses wagon 1.0-beta-5) and got an exception:

03.04.2009 16:39:34
hidden.org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request: Connection refused: connect
03.04.2009 16:39:34
hidden.org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
03.04.2009 16:39:35
hidden.org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request: Connection refused: connect
03.04.2009 16:39:35
hidden.org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: Retrying request
03.04.2009 16:39:36
hidden.org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing
request: Connection refused: connect
03.04.2009 16:39:36
hidden.org.apache.commons.httpclient.HttpMethodDirector executeWithRetry

[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error retrieving previous build number for artifact
'at.raibau:yapp:maven-plugin': repository metadata for: 'snapshot
at.raibau:yapp:0.1.2-SNAPSHOT' could not be retrieved from repository:
maven-yapp-plugin.googlecode.snapshots due to an error: Connection
refused: connect

I wrote a small Java program (using the properties https.proxyHost and
https.proxyPort) just to check if the repository url is correct, and yes,
it is correct.

Is any extra configuration needed to make webdav work behind a proxy?

Thanks

-- clovis

______________________________________
Diese E-Mail kann vertrauliche und geschuetzte Informationen enthalten. Wenn diese E-Mail nicht für Sie bestimmt ist, bitten wir Sie, uns unverzueglich zu informieren und sie zu loeschen.

This e-mail message may contain information, which is confidential and protected. If you are not the intended recipient of this message, we ask you to inform us immediately and delete the message afterwards.

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Re: Is there a workaround for WAGON-221?

2009-04-03T07:37:44Z

I cannot use maven 2.1.0. I won't list all the JIRA links that are
responsible for this decision, the fact is, I just cannot use maven 2.1.0.
That is why I asked if there is a workaround for WAGON-221.

I also know that I cannot update the wagon version to 1.0-beta-5 in my pom
(or even 1.0-beta-4) because it requires maven 2.1.0.

-- clovis

______________________________________
Diese E-Mail kann vertrauliche und geschuetzte Informationen enthalten. Wenn diese E-Mail nicht für Sie bestimmt ist, bitten wir Sie, uns unverzueglich zu informieren und sie zu loeschen.

This e-mail message may contain information, which is confidential and protected. If you are not the intended recipient of this message, we ask you to inform us immediately and delete the message afterwards.

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Is there a workaround for WAGON-221?

2009-04-03T07:19:18Z

n Fri, Apr 3, 2009 at 6:56 AM, <Clovis.SERAGIOTTO@...> wrote:

> the fix version for WAGON-221 is 1.0-beta-5, which, according to this user
> list, requires maven 1.0.x. But in the case I do need maven-2.0.9, is
> there a workaround?

According to the pom [1], Maven 2.0.9 uses Wagon 1.0-beta-2. I don't
think you can easily substitute a different version though, since it's
all bundled in lib/maven-2.0.9-uber.jar.

Try using Maven 2.1.0, which does use Wagon 1.0-beta-5.

[1] http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.9/pom.xml

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

wagon-scm:1.0-beta-5: Error checking out...

2009-04-03T07:12:41Z

Hello,

I am using maven 2.1.0 and the following configuration in my pom:

<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-scm</artifactId>
<version>1.0-beta-5</version>
</extension>
<extension>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-manager-plexus</artifactId>
<version>1.0</version>
</extension>
<extension>
<groupId>org.apache.maven.scm</groupId>
<artifactId>maven-scm-provider-svnexe</artifactId>
<version>1.0</version>
</extension>

I don't know if the configuration for the SCMs is correct; I copied it
from the pom of org.apache.maven.wagon:wagon-scm:1.0-beta-5. Anyway, when
I try to deploy the project, I get an exception:

-------------------------
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from
maven-yapp-plugin.googlecode.snapshots
[DEBUG] Connecting to repository: 'maven-yapp-plugin.googlecode.snapshots'
with url:
'scm:svn:https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots'.
[INFO] Executing: svn --username wbsser@... --password *****
09:38:17" --non-interactive checkout
https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/at/raibau/yapp/0.1.2-SNAPSHOT
0.1.2-SNAPSHOT
[INFO] Working directory:
c:\DOCUME~1\wbsser\LOCALS~1\Temp\wagon-scm1207696292.checkout\at\raibau\yapp
[INFO] repository metadata for: 'snapshot at.raibau:yapp:0.1.2-SNAPSHOT'
could not be found on repository: maven-yapp-plugin.googlecode.snapshots,
so will be created
[DEBUG] not adding permissions to wagon connection
Uploading:
scm:svn:https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/at/raibau/yapp/0.1.2-SNAPSHOT/yapp-0.1.2-20090403.134343-1.jar
[INFO] Executing: svn --username wbsser@... --password *****
09:38:17" --non-interactive list
https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/at/raibau/yapp/0.1.2-SNAPSHOT
[INFO] Working directory: c:\DOCUME~1\wbsser\LOCALS~1\Temp
[INFO] Executing: svn --username wbsser@... --password *****
09:38:17" --non-interactive list
https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/at/raibau/yapp
[INFO] Working directory: c:\DOCUME~1\wbsser\LOCALS~1\Temp
[INFO] Executing: svn --username wbsser@... --password *****
09:38:17" --non-interactive list
https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/at/raibau
[INFO] Working directory: c:\DOCUME~1\wbsser\LOCALS~1\Temp
[INFO] Executing: svn --username wbsser@... --password *****
09:38:17" --non-interactive list
https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/at
[INFO] Working directory: c:\DOCUME~1\wbsser\LOCALS~1\Temp
[INFO] Executing: svn --username wbsser@... --password *****
09:38:17" --non-interactive checkout
https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots/
wagon-scm1275150700.checkout
[INFO] Working directory: c:\DOCUME~1\wbsser\LOCALS~1\Temp
[DEBUG] Unable to commit file. The svn command failed. svn: OPTIONS of
'https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots':
authorization failed (https://maven-yapp-plugin.googlecode.com)

org.apache.maven.scm.ScmException: Unable to commit file. The svn command
failed. svn: OPTIONS of
'https://maven-yapp-plugin.googlecode.com/svn/maven2-snapshots':
authorization failed (https://maven-yapp-plugin.googlecode.com)

at
org.apache.maven.wagon.providers.scm.ScmWagon.checkScmResult(ScmWagon.java:525)
at
org.apache.maven.wagon.providers.scm.ScmWagon.checkOut(ScmWagon.java:399)
at
org.apache.maven.wagon.providers.scm.ScmWagon.putInternal(ScmWagon.java:285)
at
org.apache.maven.wagon.providers.scm.ScmWagon.put(ScmWagon.java:254)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:262)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:172)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:107)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:173)
.
.
.
-------------------------

When I input the svn checkout command myself with exactly the same
arguments (except for 09:38:17" and for the password), I have no problems.

What is the reason for the exception? Is there a workaround? And by the
way, what does 09:38:17" mean?

Thanks

-- clovis

______________________________________
Diese E-Mail kann vertrauliche und geschuetzte Informationen enthalten. Wenn diese E-Mail nicht für Sie bestimmt ist, bitten wir Sie, uns unverzueglich zu informieren und sie zu loeschen.

This e-mail message may contain information, which is confidential and protected. If you are not the intended recipient of this message, we ask you to inform us immediately and delete the message afterwards.

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Is there a workaround for WAGON-221?

2009-04-03T06:56:11Z

Hello,

the fix version for WAGON-221 is 1.0-beta-5, which, according to this user
list, requires maven 1.0.x. But in the case I do need maven-2.0.9, is
there a workaround?

Thanks

-- clovis

______________________________________
Diese E-Mail kann vertrauliche und geschuetzte Informationen enthalten. Wenn diese E-Mail nicht für Sie bestimmt ist, bitten wir Sie, uns unverzueglich zu informieren und sie zu loeschen.

This e-mail message may contain information, which is confidential and protected. If you are not the intended recipient of this message, we ask you to inform us immediately and delete the message afterwards.

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-01T08:48:01Z

maven-2.1.0 has the latest wagon, see if it works for you.

-D

On Wed, Apr 1, 2009 at 8:16 AM, Charlie Collins
<charlie.collins@...> wrote:

> I am not able to transfer files over SCP from a user/machine setup
> that is using host based authentication (note I am not talking about
> the host authentication can't be verified yes/no known_hosts issue,
> that's different - I am using host based authentication itself, not
> password, not certificate).
>
> Is host based auth supposed to work? Looks like Jsch supports it from
> the examples, but do any of the Wagon providers support it?
>
> From the client machine where Maven is running, to the server where I
> want to transfer files, using the same user account Maven is running
> as, works fine (outside of Maven):
>
> cruise@reddog:/home/ccollins$ whoami
> cruise
> cruise@reddog:/home/ccollins$ ssh helios
> Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
> cruise@helios:~$
>
> Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
> get failures using either "scp" or "scpexe" in my
> distributionManagement section (which as I understand it switches
> between ssh and ssh external Wagon providers).
>
> POM has distributionManagement set, I have tried with an without
> settings.xml server sections (beyond user/pass most of the
> "configuration" elements for the providers appear undocumented, or at
> least I couldn't find it, so I am not sure if there is a config that
> might help).
>
> POM snippet (changed back and forth from scp to scpexe for various attempts):
> <distributionManagement>
> <repository>
> <uniqueVersion>false</uniqueVersion>
> <id>axioma-maven2</id>
> <name>Axioma Maven 2 Repository</name>
> <url>scp://helios/intranet/maven2/repo</url>
> </repository>
> <snapshotRepository>
> <uniqueVersion>true</uniqueVersion>
> <id>axioma-maven2snap</id>
> <name>Axioma Maven 2 Snapshot Repository</name>
> <url>scp://helios/intranet/maven2/reposnap</url>
> </snapshotRepository>
> </distributionManagement>
>
>
> SCP failure:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
> scp://helios/intranet/maven2/reposnap
> [DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
> [DEBUG] (f) packaging = jar
> [DEBUG] (f) pomFile =
> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from axioma-maven2snap
> The authenticity of host 'helios' can't be established.
> RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
> Are you sure you want to continue connecting? (yes/no): yes
>
> (And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
> shouldn't even be trying to use that, ~/.ssh/config also exists and
> lays out the host based authentication which works perfectly with no
> prompts outside of maven.)
>
>
> SCPEXE failure:
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
> [DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
> [DEBUG] (f) attachedArtifacts = []
> [DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
> scpexe://helios/intranet/maven2/reposnap
> [DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
> [DEBUG] (f) packaging = jar
> [DEBUG] (f) pomFile =
> /opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
> [DEBUG] (f) updateReleaseInfo = false
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy]
> altDeploymentRepository = null
> [INFO] Retrieving previous build number from axioma-maven2snap
> Uploading: scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
>
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
> deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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:597)
> 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: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
> ... 16 more
> Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
> Error deploying artifact: Exit code: 1 - Warning: Identity file
> /home/cruise/.ssh/id_rsa not accessible: No such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
> at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
> ... 18 more
> Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
> 1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
> such file or directory.
> scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
> Permission denied
>
> at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
> at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
> at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
> at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
> ... 19 more
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26 seconds
> [INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
> [INFO] Final Memory: 22M/81M
> [INFO] ------------------------------------------------------------------------
>
>
> Any ideas, help, etc. I have fought with this for half a day now and
> can't come up with anything. I can get other means of auth to work
> (after jumping through some hoops and getting much deeper into this
> than I ever wanted to be), password, cert, but they aren't supported
> where I work so those won't be allowed.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Using Wagon SSH or SSH external with HOST BASED authenticaton?

2009-04-01T08:16:00Z

I am not able to transfer files over SCP from a user/machine setup
that is using host based authentication (note I am not talking about
the host authentication can't be verified yes/no known_hosts issue,
that's different - I am using host based authentication itself, not
password, not certificate).

Is host based auth supposed to work? Looks like Jsch supports it from
the examples, but do any of the Wagon providers support it?

From the client machine where Maven is running, to the server where I
want to transfer files, using the same user account Maven is running
as, works fine (outside of Maven):

cruise@reddog:/home/ccollins$ whoami
cruise
cruise@reddog:/home/ccollins$ ssh helios
Last login: Wed Apr 1 10:10:02 2009 from reddog.axiomainc.com
cruise@helios:~$

Inside of Maven, using the Deploy Plugin (which depends on Wagon), I
get failures using either "scp" or "scpexe" in my
distributionManagement section (which as I understand it switches
between ssh and ssh external Wagon providers).

POM has distributionManagement set, I have tried with an without
settings.xml server sections (beyond user/pass most of the
"configuration" elements for the providers appear undocumented, or at
least I couldn't find it, so I am not sure if there is a config that
might help).

POM snippet (changed back and forth from scp to scpexe for various attempts):
<distributionManagement>
<repository>
<uniqueVersion>false</uniqueVersion>
<id>axioma-maven2</id>
<name>Axioma Maven 2 Repository</name>
<url>scp://helios/intranet/maven2/repo</url>
</repository>
<snapshotRepository>
<uniqueVersion>true</uniqueVersion>
<id>axioma-maven2snap</id>
<name>Axioma Maven 2 Snapshot Repository</name>
<url>scp://helios/intranet/maven2/reposnap</url>
</snapshotRepository>
</distributionManagement>

SCP failure:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
[DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
scp://helios/intranet/maven2/reposnap
[DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
/opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from axioma-maven2snap
The authenticity of host 'helios' can't be established.
RSA key fingerprint is 60:af:21:b2:c7:47:b2:92:60:56:2b:27:45:a3:e8:1d.
Are you sure you want to continue connecting? (yes/no): yes

(And NOTE, the user account DOES have ~/.ssh/known_hosts, but it
shouldn't even be trying to use that, ~/.ssh/config also exists and
lays out the host based authentication which works perfectly with no
prompts outside of maven.)

SCPEXE failure:
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.3:deploy' -->
[DEBUG] (f) artifact = com.axiomainc:axioma-model:jar:0.5-SNAPSHOT
[DEBUG] (f) attachedArtifacts = []
[DEBUG] (f) deploymentRepository = [axioma-maven2snap] ->
scpexe://helios/intranet/maven2/reposnap
[DEBUG] (s) localRepository = [local] -> file:///home/cruise/.m2/repository
[DEBUG] (f) packaging = jar
[DEBUG] (f) pomFile =
/opt/hudson_home/jobs/Panacea-AxiomaModel-trunk/workspace/trunk/pom.xml
[DEBUG] (f) updateReleaseInfo = false
[DEBUG] -- end configuration --
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from axioma-maven2snap
Uploading: scpexe://helios/intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Exit code: 1 - Warning: Identity file
/home/cruise/.ssh/id_rsa not accessible: No such file or directory.
scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
Permission denied

[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error
deploying artifact: Exit code: 1 - Warning: Identity file
/home/cruise/.ssh/id_rsa not accessible: No such file or directory.
scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
Permission denied

at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:597)
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: Exit code: 1 - Warning: Identity file
/home/cruise/.ssh/id_rsa not accessible: No such file or directory.
scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
Permission denied

at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:174)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Exit code: 1 - Warning: Identity file
/home/cruise/.ssh/id_rsa not accessible: No such file or directory.
scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
Permission denied

at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
at org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:162)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Exit code:
1 - Warning: Identity file /home/cruise/.ssh/id_rsa not accessible: No
such file or directory.
scp: /intranet/maven2/reposnap/com/axiomainc/axioma-model/0.5-SNAPSHOT/axioma-model-0.5-20090401.144722-2.jar:
Permission denied

at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.executeScpCommand(ScpExternalWagon.java:236)
at org.apache.maven.wagon.providers.ssh.external.ScpExternalWagon.put(ScpExternalWagon.java:295)
at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
... 19 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 26 seconds
[INFO] Finished at: Wed Apr 01 10:47:28 EDT 2009
[INFO] Final Memory: 22M/81M
[INFO] ------------------------------------------------------------------------

Any ideas, help, etc. I have fought with this for half a day now and
can't come up with anything. I can get other means of auth to work
(after jumping through some hoops and getting much deeper into this
than I ever wanted to be), password, cert, but they aren't supported
where I work so those won't be allowed.

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SCM

2009-03-12T07:50:29Z

2009/3/12 Brett Porter <brett@...>:
> beta-4 and above require 2.1.0+ for all wagons.

Right, thanks.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Re: Using Wagon SCM

2009-03-12T04:40:44Z

beta-4 and above require 2.1.0+ for all wagons.

On 12/03/2009, at 10:30 PM, Mark Hobson wrote:

> Hi there,
>
> I was wondering what the status of wagon-scm is with regard to Maven
> 2.0.10. I've read the usage page but the versions appear to be out of
> date:
>
> http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html
>
> I've tried newer versions but end up with linking errors at runtime.
> Is there any way of using these two together or does it require a
> Wagon upgrade in Maven?
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wagon-users-unsubscribe@...
> For additional commands, e-mail: wagon-users-help@...
>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...

Using Wagon SCM

2009-03-12T04:30:45Z

Hi there,

I was wondering what the status of wagon-scm is with regard to Maven
2.0.10. I've read the usage page but the versions appear to be out of
date:

http://maven.apache.org/wagon/wagon-providers/wagon-scm/usage.html

I've tried newer versions but end up with linking errors at runtime.
Is there any way of using these two together or does it require a
Wagon upgrade in Maven?

Cheers,

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: wagon-users-unsubscribe@...
For additional commands, e-mail: wagon-users-help@...