[jira] Commented: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:

2008-02-28 Thread Bart Couvreur (JIRA)
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125517 ] Bart Couvreur commented on WAGONSSH-53: --- This issue still exists in 1.0-beta-2 After some digging, I found this: htt

[jira] Commented: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:

2007-09-19 Thread Andris Rauda (JIRA)
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107761 ] Andris Rauda commented on WAGONSSH-53: -- I have the same problem. after known_hosts were created, I'm no more prompted f

[jira] Commented: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:

2006-12-20 Thread Igor Tkach (JIRA)
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=comments#action_83078 ] Igor Tkach commented on WAGONSSH-53: One workaround to this is to use "yes" (available in Cygwin for those developing on Windows) to automate answers: yes yes | mvn d

[jira] Commented: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:

2006-12-12 Thread Igor Tkach (JIRA)
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=comments#action_82483 ] Igor Tkach commented on WAGONSSH-53: I experience the same problem. After manually adding .ssh maven does write 'known_hosts', but then it happily ignores it and keeps

[jira] Commented: (WAGONSSH-53) Error deploying artifact: Authentication failed: Cannot connect. Reason:

2006-10-19 Thread Brett Porter (JIRA)
[ http://jira.codehaus.org/browse/WAGONSSH-53?page=comments#action_78068 ] Brett Porter commented on WAGONSSH-53: -- that's quite strange if the known_hosts is correct. the issue is unresolved then. > Error deploying artifact: Authentication