[
https://jira.codehaus.org/browse/WAGON-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338628#comment-338628
]
Elliot Metsger commented on WAGON-393:
--------------------------------------
Ah. Ok, this seems to work. Instead of adding a wagon-ssh as a build
extension, add wagon-ssh as a plugin dependency to the deploy plugin:
{code}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.8.1</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh</artifactId>
<version>2.5</version>
</dependency>
</dependencies>
</plugin>
{code}
> Maven 2.2.1 fails to build when build extension uses Wagon provider > 2.2
> -------------------------------------------------------------------------
>
> Key: WAGON-393
> URL: https://jira.codehaus.org/browse/WAGON-393
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Reporter: Michael Osipov
> Priority: Critical
>
> I use the wagon-maven-plugin to upload files to SF.net. Since Maven 3 does
> not have SFTP support built-in I have declared this:
> {code}
> <extensions>
> <extension>
> <groupId>org.apache.maven.wagon</groupId>
> <artifactId>wagon-ssh</artifactId>
> <version>2.4</version>
> </extension>
> </extensions>
> {code}
> Runs fine with Maven 3 but when running with Maven 2.2.1 it says:
> {noformat}
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to initialise extensions
> Component descriptor role: 'com.jcraft.jsch.UIKeyboardInteractive',
> implementation: 'org.apache.maven.wagon.providers.ss
> h.jsch.interactive.PrompterUIKeyboardInteractive', role hint: 'default' has a
> hint, but there are other implementations
> that don't
> {noformat}
> I went down all versions to 2.2 and it worked. So there must something wrong
> from 2.2 to 2.3.
> A demo project is available.
--
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
