Re: [m1.1] Unable to deploy to remote repository

2006-07-27 Thread Daniel Beland 

This is what I have:


gdps,10.1.119.102 ssh-rsa
B3NzaC1yc2EBIwAAAIEAz44256CBVYdZPIrtoRvbl4qUuj758/U81bcMHpDK1J/6kax4lUKX4edBW38e/BvAULs0WFeP7eyMaZVQVj5NFGgRYiqkNSsfEDwc3byq/6T8dA+cSs7BzEj380SyP6It93tW40JdSEN+7TP4/kYVND/tg0UFpSPnJnXNxm9kNTk=




On 7/26/06, Lukas Theussl [EMAIL PROTECTED] wrote:


How does the line with gdps in known_hosts look like exactly? Jsch
expects a fully qualified hostname, ie something like

gdps.domain.org,xxx.xxx.xxx.xxx ssh-rsa ...

and not

gdps ssh-rsa ...

even though the latter works from the command line.

HTH,
-Lukas



Daniel Beland wrote:
 Hi,


 yes I can logon with ssh, scp and sftp works perfectly fine. I already
 accepted to add the server to my list. I can se a line for gdps in the
file
 ~/.ssh/known_hosts. I am not using authentication keys, I always type in
 the
 password.

 As I said, everything works fine with maven 1.0.2 and artifact plugin
1.5.2
 Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the
 problem.


 Since I am on windows and I run maven in cygwin, sometimes there are
 problems with the $HOME directories (my cygwin HOME is in /home of
cygwin
 and in java it is the windows home in Documents And Settings). So I
 tried to
 copy my .ssh folder in my windows HOME and it is still the same.

 Is the new artifact plugin using the ssh ant task? If so I think the
 easiest
 solution would be to add the trust property to the plugin to skip this
 security check.

 thanks,
 Daniel


 On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:


 Hi Daniel,

   Did you try to logon to your proxy host using ssh ?
 ssh -l cvs gdps

 It will certainly ask if you want to accept permanently the key.

 Arnaud


 On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote:
 
  Hi,
 
 
  I have been using maven 1.0.2 for more than a year now. I use it to
 make
  all
  of our releases on our internal repository.
  I have setup maven-proxy to access that repository and eveything
works
  fine.
 
  In my build.properties file I have the following settings:
 
  maven.repo.RF1=sftp://gdps
  maven.repo.RF1.username=cvs
  maven.repo.RF1.password=***
  maven.repo.RF1.directory=/cvs/maven/repo-local
 
 
 
  I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am
 unable
  to
  deploy something to the remote repository.
  (I tried jar:deploy, plugin:repository-deploy, etc all with the same
  exception).
 
  My configuration seems ok based on the maven-artifact-plugin doc.
  Looking on google I saw that we need to put the trust attribute to
 true,
  (if
  it is the ant task that is used by maven), but didn't find any way to
  configure it.
 
  I absolutely have to use sftp or scp.
 
 
  Here is the complete exception trace:
 
  Failed to deploy to: RF1 Reason:
  org.apache.maven.wagon.authentication.AuthenticationException: Cannot
  connect. Reason: reject HostKey: gdps
  org.apache.maven.wagon.authentication.AuthenticationException: Cannot
  connect. Reason: reject HostKey: gdps
  at
  org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
  AbstractSshWagon.java:232)
  at org.apache.maven.wagon.AbstractWagon.connect(
 AbstractWagon.java
  :143)
  at org.apache.maven.wagon.AbstractWagon.connect(
 AbstractWagon.java
  :106)
  at
 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(
  DefaultArtifactDeployer.java:372)
  at
  org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
  DefaultArtifactDeployer.java:320)
  at
 
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy
(
  DefaultArtifactDeployer.java:119)
  at
  org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
  (DefaultArtifactDeployer.java:90)
  at org.apache.maven.artifact.deployer.DeployBean.deploy(
  DeployBean.java:155)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(
  NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
  DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
  DynamicBeanTag.java:180)
  at org.apache.commons.jelly.impl.StaticTagScript.run(
  StaticTagScript.java:102)
  at org.apache.commons.jelly.impl.ScriptBlock.run(
 ScriptBlock.java
  :95)
  at org.apache.commons.jelly.impl.DynamicTag.doTag(
 DynamicTag.java
  :79)
  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
 :250)
  at org.apache.commons.jelly.impl.ScriptBlock.run(
 ScriptBlock.java
  :95)
  at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
  MavenGoalTag.java:82)
  at
 
 

org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction

  (MavenGoalTag.java:115)
  at org.apache.maven.werkz.Goal.fire(Goal.java:647)
  at

Re: [m1.1] Unable to deploy to remote repository

2006-07-27 Thread Daniel Beland 

Settping though the code to debug what was going on, I saw that wagon handle
putty (plink and pscp) differently than the rest. So I downloaded them and
changed the protocol to scpexe.

This works fine for me so I'll use that from now on.


If scp and sftp works fine for everyone else, I guess we can put the problem
on my windows+cygwin setup that does not work well with java. (It's not the
first time I see that, for example it always read my .cvspass from my
windows HOME directory even though I'm running it in cygwin. ie:
java.user.home = windows home because java doesn't know about cygwin).

So I think we can leave it as it is, though I would recommend a note on the
web site to recommend putty for windows users that want to use ssh.


Thanks for your help,
Daniel


On 7/27/06, Daniel Beland [EMAIL PROTECTED] wrote:



This is what I have:


gdps,10.1.119.102 ssh-rsa
B3NzaC1yc2EBIwAAAIEAz44256CBVYdZPIrtoRvbl4qUuj758/U81bcMHpDK1J/6kax4lUKX4edBW38e/BvAULs0WFeP7eyMaZVQVj5NFGgRYiqkNSsfEDwc3byq/6T8dA+cSs7BzEj380SyP6It93tW40JdSEN+7TP4/kYVND/tg0UFpSPnJnXNxm9kNTk=






On 7/26/06, Lukas Theussl [EMAIL PROTECTED] wrote:

 How does the line with gdps in known_hosts look like exactly? Jsch
 expects a fully qualified hostname, ie something like

 gdps.domain.org,xxx.xxx.xxx.xxx ssh-rsa ...

 and not

 gdps ssh-rsa ...

 even though the latter works from the command line.

 HTH,
 -Lukas



 Daniel Beland wrote:
  Hi,
 
 
  yes I can logon with ssh, scp and sftp works perfectly fine. I already

  accepted to add the server to my list. I can se a line for gdps in the
 file
  ~/.ssh/known_hosts. I am not using authentication keys, I always type
 in
  the
  password.
 
  As I said, everything works fine with maven 1.0.2 and artifact plugin
 1.5.2
  Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the
  problem.
 
 
  Since I am on windows and I run maven in cygwin, sometimes there are
  problems with the $HOME directories (my cygwin HOME is in /home of
 cygwin
  and in java it is the windows home in Documents And Settings). So I
  tried to
  copy my .ssh folder in my windows HOME and it is still the same.
 
  Is the new artifact plugin using the ssh ant task? If so I think the
  easiest
  solution would be to add the trust property to the plugin to skip this
  security check.
 
  thanks,
  Daniel
 
 
  On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:
 
 
  Hi Daniel,
 
Did you try to logon to your proxy host using ssh ?
  ssh -l cvs gdps
 
  It will certainly ask if you want to accept permanently the key.
 
  Arnaud
 
 
  On 7/25/06, Daniel Beland  [EMAIL PROTECTED] wrote:
  
   Hi,
  
  
   I have been using maven 1.0.2 for more than a year now. I use it to
  make
   all
   of our releases on our internal repository.
   I have setup maven-proxy to access that repository and eveything
 works
   fine.
  
   In my build.properties file I have the following settings:
  
   maven.repo.RF1=sftp://gdps
   maven.repo.RF1.username=cvs
   maven.repo.RF1.password=***
   maven.repo.RF1.directory=/cvs/maven/repo-local
  
  
  
   I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am
  unable
   to
   deploy something to the remote repository.
   (I tried jar:deploy, plugin:repository-deploy, etc all with the
 same
   exception).
  
   My configuration seems ok based on the maven-artifact-plugin doc.
   Looking on google I saw that we need to put the trust attribute to
  true,
   (if
   it is the ant task that is used by maven), but didn't find any way
 to
   configure it.
  
   I absolutely have to use sftp or scp.
  
  
   Here is the complete exception trace:
  
   Failed to deploy to: RF1 Reason:
   org.apache.maven.wagon.authentication.AuthenticationException :
 Cannot
   connect. Reason: reject HostKey: gdps
   org.apache.maven.wagon.authentication.AuthenticationException:
 Cannot
   connect. Reason: reject HostKey: gdps
   at
  
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
   AbstractSshWagon.java:232)
   at org.apache.maven.wagon.AbstractWagon.connect(
  AbstractWagon.java
   :143)
   at org.apache.maven.wagon.AbstractWagon.connect(
  AbstractWagon.java
   :106)
   at
  
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles (
   DefaultArtifactDeployer.java:372)
   at
   org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy
 (
   DefaultArtifactDeployer.java:320)
   at
  
 
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(
   DefaultArtifactDeployer.java:119)
   at
   org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
   (DefaultArtifactDeployer.java:90)
   at org.apache.maven.artifact.deployer.DeployBean.deploy(
   DeployBean.java :155)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
 Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
   NativeMethodAccessorImpl.java:39)

Re: [m1.1] Unable to deploy to remote repository

2006-07-26 Thread Daniel Beland 

Hi,


yes I can logon with ssh, scp and sftp works perfectly fine. I already
accepted to add the server to my list. I can se a line for gdps in the file
~/.ssh/known_hosts. I am not using authentication keys, I always type in the
password.

As I said, everything works fine with maven 1.0.2 and artifact plugin 1.5.2
Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the problem.


Since I am on windows and I run maven in cygwin, sometimes there are
problems with the $HOME directories (my cygwin HOME is in /home of cygwin
and in java it is the windows home in Documents And Settings). So I tried to
copy my .ssh folder in my windows HOME and it is still the same.

Is the new artifact plugin using the ssh ant task? If so I think the easiest
solution would be to add the trust property to the plugin to skip this
security check.

thanks,
Daniel


On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:


Hi Daniel,

  Did you try to logon to your proxy host using ssh ?
ssh -l cvs gdps

It will certainly ask if you want to accept permanently the key.

Arnaud


On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote:

 Hi,


 I have been using maven 1.0.2 for more than a year now. I use it to make
 all
 of our releases on our internal repository.
 I have setup maven-proxy to access that repository and eveything works
 fine.

 In my build.properties file I have the following settings:

 maven.repo.RF1=sftp://gdps
 maven.repo.RF1.username=cvs
 maven.repo.RF1.password=***
 maven.repo.RF1.directory=/cvs/maven/repo-local



 I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am
unable
 to
 deploy something to the remote repository.
 (I tried jar:deploy, plugin:repository-deploy, etc all with the same
 exception).

 My configuration seems ok based on the maven-artifact-plugin doc.
 Looking on google I saw that we need to put the trust attribute to true,
 (if
 it is the ant task that is used by maven), but didn't find any way to
 configure it.

 I absolutely have to use sftp or scp.


 Here is the complete exception trace:

 Failed to deploy to: RF1 Reason:
 org.apache.maven.wagon.authentication.AuthenticationException: Cannot
 connect. Reason: reject HostKey: gdps
 org.apache.maven.wagon.authentication.AuthenticationException: Cannot
 connect. Reason: reject HostKey: gdps
 at
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
 AbstractSshWagon.java:232)
 at org.apache.maven.wagon.AbstractWagon.connect(
AbstractWagon.java
 :143)
 at org.apache.maven.wagon.AbstractWagon.connect(
AbstractWagon.java
 :106)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(
 DefaultArtifactDeployer.java:372)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
 DefaultArtifactDeployer.java:320)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(
 DefaultArtifactDeployer.java:119)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
 (DefaultArtifactDeployer.java:90)
 at org.apache.maven.artifact.deployer.DeployBean.deploy(
 DeployBean.java:155)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
 DynamicBeanTag.java:180)
 at org.apache.commons.jelly.impl.StaticTagScript.run(
 StaticTagScript.java:102)
 at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
 :95)
 at org.apache.commons.jelly.impl.DynamicTag.doTag(
DynamicTag.java
 :79)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
:250)
 at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
 :95)
 at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
 MavenGoalTag.java:82)
 at


org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction
 (MavenGoalTag.java:115)
 at org.apache.maven.werkz.Goal.fire(Goal.java:647)
 at org.apache.maven.werkz.Goal.attain(Goal.java:582)
 at org.apache.maven.plugin.PluginManager.attainGoals(
 PluginManager.java:709)
 at org.apache.maven.MavenSession.attainGoals(MavenSession.java
 :264)
 at org.apache.maven.cli.App.doMain(App.java:546)
 at org.apache.maven.cli.App.main(App.java:1359)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at com.werken.forehead.Forehead.run(Forehead.java:551)

Re: [m1.1] Unable to deploy to remote repository

2006-07-26 Thread Arnaud HERITIER 

The new artifact plugin uses the wagon project.
I must have a look at the code to see how it works.

Can you try the version 1.9-SNAPSHOT please?


maven plugin:download -DgroupId=maven
-DartifactId=*maven-artifact-plugin* -Dversion=*1.9*-SNAPSHOT
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://people.apache.org/repo/m1-snapshot-repository/

Cheers,

Arnaud





On 7/26/06, Daniel Beland [EMAIL PROTECTED] wrote:


Hi,


yes I can logon with ssh, scp and sftp works perfectly fine. I already
accepted to add the server to my list. I can se a line for gdps in the
file
~/.ssh/known_hosts. I am not using authentication keys, I always type in
the
password.

As I said, everything works fine with maven 1.0.2 and artifact plugin
1.5.2
Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the
problem.


Since I am on windows and I run maven in cygwin, sometimes there are
problems with the $HOME directories (my cygwin HOME is in /home of cygwin
and in java it is the windows home in Documents And Settings). So I tried
to
copy my .ssh folder in my windows HOME and it is still the same.

Is the new artifact plugin using the ssh ant task? If so I think the
easiest
solution would be to add the trust property to the plugin to skip this
security check.

thanks,
Daniel


On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:

 Hi Daniel,

   Did you try to logon to your proxy host using ssh ?
 ssh -l cvs gdps

 It will certainly ask if you want to accept permanently the key.

 Arnaud


 On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote:
 
  Hi,
 
 
  I have been using maven 1.0.2 for more than a year now. I use it to
make
  all
  of our releases on our internal repository.
  I have setup maven-proxy to access that repository and eveything works
  fine.
 
  In my build.properties file I have the following settings:
 
  maven.repo.RF1=sftp://gdps
  maven.repo.RF1.username=cvs
  maven.repo.RF1.password=***
  maven.repo.RF1.directory=/cvs/maven/repo-local
 
 
 
  I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am
 unable
  to
  deploy something to the remote repository.
  (I tried jar:deploy, plugin:repository-deploy, etc all with the same
  exception).
 
  My configuration seems ok based on the maven-artifact-plugin doc.
  Looking on google I saw that we need to put the trust attribute to
true,
  (if
  it is the ant task that is used by maven), but didn't find any way to
  configure it.
 
  I absolutely have to use sftp or scp.
 
 
  Here is the complete exception trace:
 
  Failed to deploy to: RF1 Reason:
  org.apache.maven.wagon.authentication.AuthenticationException: Cannot
  connect. Reason: reject HostKey: gdps
  org.apache.maven.wagon.authentication.AuthenticationException: Cannot
  connect. Reason: reject HostKey: gdps
  at
  org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
  AbstractSshWagon.java:232)
  at org.apache.maven.wagon.AbstractWagon.connect(
 AbstractWagon.java
  :143)
  at org.apache.maven.wagon.AbstractWagon.connect(
 AbstractWagon.java
  :106)
  at
  org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles
(
  DefaultArtifactDeployer.java:372)
  at
  org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
  DefaultArtifactDeployer.java:320)
  at
 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(
  DefaultArtifactDeployer.java:119)
  at
  org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
  (DefaultArtifactDeployer.java:90)
  at org.apache.maven.artifact.deployer.DeployBean.deploy(
  DeployBean.java:155)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(
  NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(
  DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:324)
  at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
  DynamicBeanTag.java:180)
  at org.apache.commons.jelly.impl.StaticTagScript.run(
  StaticTagScript.java:102)
  at org.apache.commons.jelly.impl.ScriptBlock.run(
 ScriptBlock.java
  :95)
  at org.apache.commons.jelly.impl.DynamicTag.doTag(
 DynamicTag.java
  :79)
  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
 :250)
  at org.apache.commons.jelly.impl.ScriptBlock.run(
 ScriptBlock.java
  :95)
  at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
  MavenGoalTag.java:82)
  at
 
 

org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction
  (MavenGoalTag.java:115)
  at org.apache.maven.werkz.Goal.fire(Goal.java:647)
  at org.apache.maven.werkz.Goal.attain(Goal.java:582)
  at org.apache.maven.plugin.PluginManager.attainGoals(
  PluginManager.java:709)
  at

Re: [m1.1] Unable to deploy to remote repository

2006-07-26 Thread Daniel Beland 

Sorry I was using 1.8 and not 1.7 as I said.
1.9-SNAPSHOT gives me the same error.



On 7/26/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:


The new artifact plugin uses the wagon project.
I must have a look at the code to see how it works.

Can you try the version 1.9-SNAPSHOT please?


maven plugin:download -DgroupId=maven
-DartifactId=*maven-artifact-plugin* -Dversion=*1.9*-SNAPSHOT
-Dmaven.repo.remote=http://www.ibiblio.org/maven,
http://people.apache.org/repo/m1-snapshot-repository/

Cheers,

Arnaud





On 7/26/06, Daniel Beland [EMAIL PROTECTED] wrote:

 Hi,


 yes I can logon with ssh, scp and sftp works perfectly fine. I already
 accepted to add the server to my list. I can se a line for gdps in the
 file
 ~/.ssh/known_hosts. I am not using authentication keys, I always type in
 the
 password.

 As I said, everything works fine with maven 1.0.2 and artifact plugin
 1.5.2
 Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the
 problem.


 Since I am on windows and I run maven in cygwin, sometimes there are
 problems with the $HOME directories (my cygwin HOME is in /home of
cygwin
 and in java it is the windows home in Documents And Settings). So I
tried
 to
 copy my .ssh folder in my windows HOME and it is still the same.

 Is the new artifact plugin using the ssh ant task? If so I think the
 easiest
 solution would be to add the trust property to the plugin to skip this
 security check.

 thanks,
 Daniel


 On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:
 
  Hi Daniel,
 
Did you try to logon to your proxy host using ssh ?
  ssh -l cvs gdps
 
  It will certainly ask if you want to accept permanently the key.
 
  Arnaud
 
 
  On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote:
  
   Hi,
  
  
   I have been using maven 1.0.2 for more than a year now. I use it to
 make
   all
   of our releases on our internal repository.
   I have setup maven-proxy to access that repository and eveything
works
   fine.
  
   In my build.properties file I have the following settings:
  
   maven.repo.RF1=sftp://gdps
   maven.repo.RF1.username=cvs
   maven.repo.RF1.password=***
   maven.repo.RF1.directory=/cvs/maven/repo-local
  
  
  
   I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am
  unable
   to
   deploy something to the remote repository.
   (I tried jar:deploy, plugin:repository-deploy, etc all with the same
   exception).
  
   My configuration seems ok based on the maven-artifact-plugin doc.
   Looking on google I saw that we need to put the trust attribute to
 true,
   (if
   it is the ant task that is used by maven), but didn't find any way
to
   configure it.
  
   I absolutely have to use sftp or scp.
  
  
   Here is the complete exception trace:
  
   Failed to deploy to: RF1 Reason:
   org.apache.maven.wagon.authentication.AuthenticationException:
Cannot
   connect. Reason: reject HostKey: gdps
   org.apache.maven.wagon.authentication.AuthenticationException:
Cannot
   connect. Reason: reject HostKey: gdps
   at
   org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection
(
   AbstractSshWagon.java:232)
   at org.apache.maven.wagon.AbstractWagon.connect(
  AbstractWagon.java
   :143)
   at org.apache.maven.wagon.AbstractWagon.connect(
  AbstractWagon.java
   :106)
   at
  
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles
 (
   DefaultArtifactDeployer.java:372)
   at
   org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
   DefaultArtifactDeployer.java:320)
   at
  
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(
   DefaultArtifactDeployer.java:119)
   at
   org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
   (DefaultArtifactDeployer.java:90)
   at org.apache.maven.artifact.deployer.DeployBean.deploy(
   DeployBean.java:155)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
   NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(
   DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
   DynamicBeanTag.java:180)
   at org.apache.commons.jelly.impl.StaticTagScript.run(
   StaticTagScript.java:102)
   at org.apache.commons.jelly.impl.ScriptBlock.run(
  ScriptBlock.java
   :95)
   at org.apache.commons.jelly.impl.DynamicTag.doTag(
  DynamicTag.java
   :79)
   at org.apache.commons.jelly.impl.TagScript.run(
TagScript.java
  :250)
   at org.apache.commons.jelly.impl.ScriptBlock.run(
  ScriptBlock.java
   :95)
   at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag
(
   MavenGoalTag.java:82)
   at
  
  
 

org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction

Re: [m1.1] Unable to deploy to remote repository

2006-07-26 Thread Lukas Theussl 
How does the line with gdps in known_hosts look like exactly? Jsch 
expects a fully qualified hostname, ie something like


gdps.domain.org,xxx.xxx.xxx.xxx ssh-rsa ...

and not

gdps ssh-rsa ...

even though the latter works from the command line.

HTH,
-Lukas



Daniel Beland wrote:

Hi,


yes I can logon with ssh, scp and sftp works perfectly fine. I already
accepted to add the server to my list. I can se a line for gdps in the file
~/.ssh/known_hosts. I am not using authentication keys, I always type in 
the

password.

As I said, everything works fine with maven 1.0.2 and artifact plugin 1.5.2
Moving to maven 1.1-beta3 and artifact plugin 1.7 is causing me the 
problem.



Since I am on windows and I run maven in cygwin, sometimes there are
problems with the $HOME directories (my cygwin HOME is in /home of cygwin
and in java it is the windows home in Documents And Settings). So I 
tried to

copy my .ssh folder in my windows HOME and it is still the same.

Is the new artifact plugin using the ssh ant task? If so I think the 
easiest

solution would be to add the trust property to the plugin to skip this
security check.

thanks,
Daniel


On 7/25/06, Arnaud HERITIER [EMAIL PROTECTED] wrote:



Hi Daniel,

  Did you try to logon to your proxy host using ssh ?
ssh -l cvs gdps

It will certainly ask if you want to accept permanently the key.

Arnaud


On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote:

 Hi,


 I have been using maven 1.0.2 for more than a year now. I use it to 
make

 all
 of our releases on our internal repository.
 I have setup maven-proxy to access that repository and eveything works
 fine.

 In my build.properties file I have the following settings:

 maven.repo.RF1=sftp://gdps
 maven.repo.RF1.username=cvs
 maven.repo.RF1.password=***
 maven.repo.RF1.directory=/cvs/maven/repo-local



 I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am
unable
 to
 deploy something to the remote repository.
 (I tried jar:deploy, plugin:repository-deploy, etc all with the same
 exception).

 My configuration seems ok based on the maven-artifact-plugin doc.
 Looking on google I saw that we need to put the trust attribute to 
true,

 (if
 it is the ant task that is used by maven), but didn't find any way to
 configure it.

 I absolutely have to use sftp or scp.


 Here is the complete exception trace:

 Failed to deploy to: RF1 Reason:
 org.apache.maven.wagon.authentication.AuthenticationException: Cannot
 connect. Reason: reject HostKey: gdps
 org.apache.maven.wagon.authentication.AuthenticationException: Cannot
 connect. Reason: reject HostKey: gdps
 at
 org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
 AbstractSshWagon.java:232)
 at org.apache.maven.wagon.AbstractWagon.connect(
AbstractWagon.java
 :143)
 at org.apache.maven.wagon.AbstractWagon.connect(
AbstractWagon.java
 :106)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(
 DefaultArtifactDeployer.java:372)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
 DefaultArtifactDeployer.java:320)
 at
 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(

 DefaultArtifactDeployer.java:119)
 at
 org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
 (DefaultArtifactDeployer.java:90)
 at org.apache.maven.artifact.deployer.DeployBean.deploy(
 DeployBean.java:155)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(
 NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(
 DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
 DynamicBeanTag.java:180)
 at org.apache.commons.jelly.impl.StaticTagScript.run(
 StaticTagScript.java:102)
 at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
 :95)
 at org.apache.commons.jelly.impl.DynamicTag.doTag(
DynamicTag.java
 :79)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java
:250)
 at org.apache.commons.jelly.impl.ScriptBlock.run(
ScriptBlock.java
 :95)
 at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
 MavenGoalTag.java:82)
 at


org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction 


 (MavenGoalTag.java:115)
 at org.apache.maven.werkz.Goal.fire(Goal.java:647)
 at org.apache.maven.werkz.Goal.attain(Goal.java:582)
 at org.apache.maven.plugin.PluginManager.attainGoals(
 PluginManager.java:709)
 at org.apache.maven.MavenSession.attainGoals(MavenSession.java
 :264)
 at org.apache.maven.cli.App.doMain(App.java:546)
 at org.apache.maven.cli.App.main(App.java:1359)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at

[m1.1] Unable to deploy to remote repository

2006-07-25 Thread Daniel Beland 

Hi,


I have been using maven 1.0.2 for more than a year now. I use it to make all
of our releases on our internal repository.
I have setup maven-proxy to access that repository and eveything works fine.

In my build.properties file I have the following settings:

maven.repo.RF1=sftp://gdps
maven.repo.RF1.username=cvs
maven.repo.RF1.password=***
maven.repo.RF1.directory=/cvs/maven/repo-local



I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable to
deploy something to the remote repository.
(I tried jar:deploy, plugin:repository-deploy, etc all with the same
exception).

My configuration seems ok based on the maven-artifact-plugin doc.
Looking on google I saw that we need to put the trust attribute to true, (if
it is the ant task that is used by maven), but didn't find any way to
configure it.

I absolutely have to use sftp or scp.


Here is the complete exception trace:

Failed to deploy to: RF1 Reason:
org.apache.maven.wagon.authentication.AuthenticationException: Cannot
connect. Reason: reject HostKey: gdps
org.apache.maven.wagon.authentication.AuthenticationException: Cannot
connect. Reason: reject HostKey: gdps
   at
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
AbstractSshWagon.java:232)
   at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java
:143)
   at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java
:106)
   at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(
DefaultArtifactDeployer.java:372)
   at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
DefaultArtifactDeployer.java:320)
   at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(
DefaultArtifactDeployer.java:119)
   at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:90)
   at org.apache.maven.artifact.deployer.DeployBean.deploy(
DeployBean.java:155)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
DynamicBeanTag.java:180)
   at org.apache.commons.jelly.impl.StaticTagScript.run(
StaticTagScript.java:102)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java
:95)
   at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java
:79)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java
:95)
   at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
MavenGoalTag.java:82)
   at
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction
(MavenGoalTag.java:115)
   at org.apache.maven.werkz.Goal.fire(Goal.java:647)
   at org.apache.maven.werkz.Goal.attain(Goal.java:582)
   at org.apache.maven.plugin.PluginManager.attainGoals(
PluginManager.java:709)
   at org.apache.maven.MavenSession.attainGoals(MavenSession.java:264)
   at org.apache.maven.cli.App.doMain(App.java:546)
   at org.apache.maven.cli.App.main(App.java:1359)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at com.werken.forehead.Forehead.run(Forehead.java:551)
   at com.werken.forehead.Forehead.main(Forehead.java:581)
Caused by: com.jcraft.jsch.JSchException: reject HostKey: gdps
   at com.jcraft.jsch.Session.checkHost(Unknown Source)
   at com.jcraft.jsch.Session.connect(Unknown Source)
   at com.jcraft.jsch.Session.connect(Unknown Source)
   at
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
AbstractSshWagon.java:221)
   ... 31 more

Thanks,
Daniel

Re: [m1.1] Unable to deploy to remote repository

2006-07-25 Thread Arnaud HERITIER 

Hi Daniel,

 Did you try to logon to your proxy host using ssh ?
ssh -l cvs gdps

It will certainly ask if you want to accept permanently the key.

Arnaud


On 7/25/06, Daniel Beland [EMAIL PROTECTED] wrote:


Hi,


I have been using maven 1.0.2 for more than a year now. I use it to make
all
of our releases on our internal repository.
I have setup maven-proxy to access that repository and eveything works
fine.

In my build.properties file I have the following settings:

maven.repo.RF1=sftp://gdps
maven.repo.RF1.username=cvs
maven.repo.RF1.password=***
maven.repo.RF1.directory=/cvs/maven/repo-local



I tried to migrate to maven 1.1-beta3-SNAPSHOT (20060723) and I am unable
to
deploy something to the remote repository.
(I tried jar:deploy, plugin:repository-deploy, etc all with the same
exception).

My configuration seems ok based on the maven-artifact-plugin doc.
Looking on google I saw that we need to put the trust attribute to true,
(if
it is the ant task that is used by maven), but didn't find any way to
configure it.

I absolutely have to use sftp or scp.


Here is the complete exception trace:

Failed to deploy to: RF1 Reason:
org.apache.maven.wagon.authentication.AuthenticationException: Cannot
connect. Reason: reject HostKey: gdps
org.apache.maven.wagon.authentication.AuthenticationException: Cannot
connect. Reason: reject HostKey: gdps
at
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
AbstractSshWagon.java:232)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java
:143)
at org.apache.maven.wagon.AbstractWagon.connect(AbstractWagon.java
:106)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles(
DefaultArtifactDeployer.java:372)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(
DefaultArtifactDeployer.java:320)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(
DefaultArtifactDeployer.java:119)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy
(DefaultArtifactDeployer.java:90)
at org.apache.maven.artifact.deployer.DeployBean.deploy(
DeployBean.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(
DynamicBeanTag.java:180)
at org.apache.commons.jelly.impl.StaticTagScript.run(
StaticTagScript.java:102)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java
:95)
at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java
:79)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:250)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java
:95)
at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(
MavenGoalTag.java:82)
at

org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction
(MavenGoalTag.java:115)
at org.apache.maven.werkz.Goal.fire(Goal.java:647)
at org.apache.maven.werkz.Goal.attain(Goal.java:582)
at org.apache.maven.plugin.PluginManager.attainGoals(
PluginManager.java:709)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java
:264)
at org.apache.maven.cli.App.doMain(App.java:546)
at org.apache.maven.cli.App.main(App.java:1359)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Caused by: com.jcraft.jsch.JSchException: reject HostKey: gdps
at com.jcraft.jsch.Session.checkHost(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at com.jcraft.jsch.Session.connect(Unknown Source)
at
org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(
AbstractSshWagon.java:221)
... 31 more

Thanks,
Daniel