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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
