[ http://jira.codehaus.org/browse/MPARTIFACT-71?page=comments#action_72014
]
Stephane Nicoll commented on MPARTIFACT-71:
-------------------------------------------
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:
{noformat}
maven.repo.list=rd
maven.repo.rd=file://\\\\serverX\\
maven.repo.rd.directory=maven-artifacts
{noformat}
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.
> Can't deploy artifacts due to "reject HostKey" error
> ----------------------------------------------------
>
> Key: MPARTIFACT-71
> URL: http://jira.codehaus.org/browse/MPARTIFACT-71
> Project: maven-artifact-plugin
> Issue Type: Bug
> Environment: Client=Win XP; Maven 1.1b3; deploying tasks 1.3-snapshot
> to maven-plugins at SourceForge
> Reporter: Jeff Jensen
> Priority: Blocker
>
> 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).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
