[
https://issues.apache.org/jira/browse/WAGON-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15697162#comment-15697162
]
ASF GitHub Bot commented on WAGON-467:
--------------------------------------
Github user nfalco79 commented on the issue:
https://github.com/apache/maven-wagon/pull/29
Debugging a log the issue seems to be which implementation of WagonManger
plexus inject. If I run with maven 3.3.9 it injects a
[DefaultWagonManager](http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven/maven-compat/3.3.3/org/apache/maven/repository/legacy/DefaultWagonManager.java#DefaultWagonManager.getWagon%28org.apache.maven.wagon.repository.Repository%29)
where the getWagon is deprecated and lacks of configureWagon call that do the
trick above. If I run it with maven 2.2.1 it has a working implementation of
[DefaultWagonManager](http://grepcode.com/file/repo1.maven.org/maven2/org.apache.maven/maven-artifact-manager/2.2.1/org/apache/maven/artifact/manager/DefaultWagonManager.java#DefaultWagonManager.getWagon%28org.apache.maven.wagon.repository.Repository%29)
but mvn command breaks with the following message:
```
[INFO] Unable to initialise extensions
Component descriptor role: 'com.jcraft.jsch.UIKeyboardInteractive',
implementation:
'org.apache.maven.wagon.providers.ssh.jsch.interactive.PrompterUIKeyboardInteractive',
role hint: 'default' has a hint, but there are other implementations that don't
```
This explains the reason of extra work in the maven-site-plugin around
configureWagon method to distinguish of maven 2/3
I hope these information will help you to make a workaround for your
wagon-maven-plugin
> wagon-ssh: options to configure hostKeyChecking and PreferredAuthentications
> -----------------------------------------------------------------------------
>
> Key: WAGON-467
> URL: https://issues.apache.org/jira/browse/WAGON-467
> Project: Maven Wagon
> Issue Type: Improvement
> Components: wagon-ssh
> Affects Versions: 2.10
> Environment: Maven 3.3
> Jenkins
> Reporter: Nikolas Falco
> Assignee: Dan Tran
> Fix For: 2.11
>
>
> Hi,
> I'm looking a way to deploy the maven site using scp protocol.
> I found some issues:
> * when I create a Jenkins node the maven process stucks during site:deploy
> goal because it prompts to me if I want add the destination host key to
> know_hosts file.
> * also with correct credential in settings.xml it prompts to me for Kerberos
> username [$USER] and password.
> After a lot of google search the SSH options command to setup should be:
> * StrictHostKeyChecking [ask, no, yes]
> * PreferredAuthentications a mix of [gssapi-with-mic, publickey, password,
> keyboard-interactive]
> Configure those option into them into .ssh/config file it's hard to manage in
> many in case of many machine
> Actually there is not way to change those settings in the wagon instance
> For StrictHostKeyChecking could be used the settings.xml
> {code:xml}
> <servers>
> <server>
> <id>docserver</id>
> <username>xxx</username>
> <password>password</password>
> <configuration>
> <knownHostsProvider>
> <hostKeyChecking>no</hostKeyChecking>
> </knownHostsProvider>
> </configuration>
> </server>
> </servers>
> {code}
> but it fails because KnownHostsProvider it's an interface and if I specify
> the implementation of knownHostsProvider
> {code:xml}
> <knownHostsProvider
> implementation="org.apache.maven.wagon.providers.ssh.knownhost.FileKnownHostsProvider">
> {code}
> fails because ClassNotFound on IOUtil in super constructor method.
> Instead for PreferredAuthentications it's an plain string into the code so no
> way to change it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
