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.

Related threads on the user list:

http://www.nabble.com/-m1.1--Unable-to-deploy-to-remote-repository-tf1998533.html#a5486207
http://www.nabble.com/Maven-1.1-beta3---maven-artifact-plugin-1.8-tf2078440.html#a5724767
http://www.nabble.com/-m1--unable-to-run-jar%3Adeploy-using-maven-1.1-beta3-tf2083637.html

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

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.

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

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.

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.

Jeff found that this bug exists also with the sftp protocol

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

Good job Arnaud, the new snapshot works for SFTP.