Maven 1.x Artifact Plugin

Can't deploy artifacts due to "reject HostKey" error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.8
  • Fix Version/s: 1.9
  • Component/s: None
  • Labels:
    None
  • Environment:
    Client=Win XP; Maven 1.1b3; deploying tasks 1.3-snapshot to maven-plugins at SourceForge
  • Number of attachments :
    0

Description

This is the high-level error info:

plugin:repository-deploy:
[echo] Deploying...
Will deploy to 1 repository(ies): maven.plugins.sf.snapshots
Deploying to repository: maven.plugins.sf.snapshots
Failed to deploy to: maven.plugins.sf.snapshots Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: shell.sourceforge.net
org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: shell.sourceforge.net
at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection(AbstractSshWagon.java:232)

If I use m1.1b3-snapshot of 6/30 from Arnaud's website, it works. Any snapshot after that and the b3 release do not work - they have this problem.

I think (but not sure) one key procedure to reproducing this is to start with clean repo and plugins install area: delete the .maven dir and any existing Maven program dir (the plugins must start with only the bundled ones).

Issue Links

This issue is related to:
MPARTIFACT-61 scpexe is a noop Blocker Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Stephane Nicoll added a comment -

Also problem with file system deployment:

On SERVERX, I have a shared directory named 'maven-artifacts' (so \\SERVERX\maven-artifacts maps to the root of the maven repository)

Here's my configuration:

maven.repo.list=rd
maven.repo.rd=file://\\\\serverX\\
maven.repo.rd.directory=maven-artifacts

Running m 1.0.2 without Wagon (so an old version of the artifact plugin) is running OK. If I upgrade (both m1.0.2 and m1.1) the deployment is running fine (no error) but nothing is deployed on the repository !

I will reproduce the problem ASAP and provide a debug log.

Show
Stephane Nicoll added a comment - Also problem with file system deployment: On SERVERX, I have a shared directory named 'maven-artifacts' (so \\SERVERX\maven-artifacts maps to the root of the maven repository) Here's my configuration: 
maven.repo.list=rd
maven.repo.rd=file://\\\\serverX\\
maven.repo.rd.directory=maven-artifacts
Running m 1.0.2 without Wagon (so an old version of the artifact plugin) is running OK. If I upgrade (both m1.0.2 and m1.1) the deployment is running fine (no error) but nothing is deployed on the repository ! I will reproduce the problem ASAP and provide a debug log.
Hide
Permalink
Siegfried Goeschl added a comment -

Hi folks,

I work on Windoxs XP box using a Linux box as repository

maven-1.1-beta3
===============================================================

the deployment with maven-1.1-beta3 the deployment fails with

Will deploy to 1 repository(ies): releases
Deploying to repository: releases
Failed to deploy to: releases Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostK
org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: 10.0.0.25
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)

maven-2.0.4
===============================================================

works

ant
===============================================================

using the optional scp task and jsch-0.1.14.jar works

Show
Siegfried Goeschl added a comment - Hi folks, I work on Windoxs XP box using a Linux box as repository maven-1.1-beta3 =============================================================== the deployment with maven-1.1-beta3 the deployment fails with Will deploy to 1 repository(ies): releases Deploying to repository: releases Failed to deploy to: releases Reason: org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostK org.apache.maven.wagon.authentication.AuthenticationException: Cannot connect. Reason: reject HostKey: 10.0.0.25 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) maven-2.0.4 =============================================================== works ant =============================================================== using the optional scp task and jsch-0.1.14.jar works
Hide
Permalink
Steve Molloy added a comment -

Got the same behaviour after updating to 1.1-beta3 on Fedora cor5, using Sun JDK 1.5.0_07. Plain scp failed because of host key rejected, while scpexe just silently did nothing...

Checked out trunk of maven-artifact-plugin, compiled and replaced the cached classes, both scp and scpexe work fine.

Show
Steve Molloy added a comment - Got the same behaviour after updating to 1.1-beta3 on Fedora cor5, using Sun JDK 1.5.0_07. Plain scp failed because of host key rejected, while scpexe just silently did nothing... Checked out trunk of maven-artifact-plugin, compiled and replaced the cached classes, both scp and scpexe work fine.
Hide
Permalink
Arnaud Heritier added a comment -

I just deployed the SNAPSHOT of the version 1.8.1. You can test it with maven 1.1 beta 3

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

It should fix the problem.
When I upgraded wagon dependencies I changed a little bit the plugin's code to not have this error of RejectedKey.
The problem Is that in the beta 3 we upgraded these dependencies (through the core) but we don't bundle the new artifact plugin

https://svn.apache.org/viewvc/maven/maven-1/plugins/trunk/artifact/src/main/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java?sortdir=down&r1=350092&r2=409253
https://svn.apache.org/viewvc/maven/maven-1/plugins/trunk/artifact/src/main/org/apache/maven/artifact/deployer/RepositoryBuilder.java?sortdir=down&r1=233442&r2=409253

Show
Arnaud Heritier added a comment - I just deployed the SNAPSHOT of the version 1.8.1. You can test it with maven 1.1 beta 3 maven plugin:download -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion=1.8.1-SNAPSHOT -Dmaven.repo.remote=http://www.ibiblio.org/maven ,http://people.apache.org/repo/m1-snapshot-repository/ It should fix the problem. When I upgraded wagon dependencies I changed a little bit the plugin's code to not have this error of RejectedKey. The problem Is that in the beta 3 we upgraded these dependencies (through the core) but we don't bundle the new artifact plugin https://svn.apache.org/viewvc/maven/maven-1/plugins/trunk/artifact/src/main/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java?sortdir=down&r1=350092&r2=409253 https://svn.apache.org/viewvc/maven/maven-1/plugins/trunk/artifact/src/main/org/apache/maven/artifact/deployer/RepositoryBuilder.java?sortdir=down&r1=233442&r2=409253
Hide
Permalink
Jeff Jensen added a comment -

Works for me! Great job Arnaud!

I ran plugin:download as you have above, then ran maven -Dmaven.repo.list=maven.plugins.sf.snapshots plugin:repository-deploy, and it deployed.

Show
Jeff Jensen added a comment - Works for me! Great job Arnaud! I ran plugin:download as you have above, then ran maven -Dmaven.repo.list=maven.plugins.sf.snapshots plugin:repository-deploy, and it deployed.
Hide
Permalink
Arnaud Heritier added a comment -

It's fixed. Host key is always accepted.
scpexe protocol works for me. If you encounter again this bug with scpexe, please open a new bug.

Show
Arnaud Heritier added a comment - It's fixed. Host key is always accepted. scpexe protocol works for me. If you encounter again this bug with scpexe, please open a new bug.
Hide
Permalink
Arnaud Heritier added a comment -

Jeff found that this bug exists also with the sftp protocol

Show
Arnaud Heritier added a comment - Jeff found that this bug exists also with the sftp protocol
Hide
Permalink
Arnaud Heritier added a comment -

Fixed also for SFTP protocol. A new snapshot of the plugin is deployed with this protocol

Show
Arnaud Heritier added a comment - Fixed also for SFTP protocol. A new snapshot of the plugin is deployed with this protocol
Hide
Permalink
Jeff Jensen added a comment -

Good job Arnaud, the new snapshot works for SFTP.

Show
Jeff Jensen added a comment - Good job Arnaud, the new snapshot works for SFTP.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.