You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jelle De Vreese (JIRA)" <ji...@codehaus.org> on 2013/03/25 11:21:53 UTC
[jira] (WAGON-391) Error installing artifact's metadata: Error
while deploying metadata: Authentication failed: Cannot connect. Reason:
verify: false
[ https://jira.codehaus.org/browse/WAGON-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322574#comment-322574 ]
Jelle De Vreese commented on WAGON-391:
---------------------------------------
According to [this message from Atsuhiko Yamanaka|http://www.mailinglistarchive.com/html/jsch-users@lists.sourceforge.net/2013-02/msg00006.html], the problem is caused by a change in behaviour in Java 7 update 6.
It looks like the problem will be fixed in jsch 0.1.50.
> Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: WAGON-391
> URL: https://jira.codehaus.org/browse/WAGON-391
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Affects Versions: 2.3
> Reporter: Bryan Kelly
>
> When attempting to publish an artifact to an ssh server we get the following exception intermittently:
> Error installing artifact's metadata: Error while deploying metadata: Authentication failed: Cannot connect. Reason: verify: false
> Other consumers of the jsch library have had a similar issue [1], their fix was to add retry logic while attempting to make the connection to the ssh server.
> [1] https://github.com/int128/gradle-ssh-plugin/issues/11
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira