[
https://issues.apache.org/jira/browse/WAGON-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522858#comment-17522858
]
Curtis Rueden commented on WAGON-616:
-------------------------------------
Ah, thank you, I understand now that sshexe and scpexe mean wagon-ssh-external,
as explained in the [Deployment of artifacts in an external SSH
command|https://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-external.html]
guide. Thank you for your patience, and the helpful links!
I have now updated [my SO answer|https://stackoverflow.com/a/14404990/1207769]
to explain the current situation, as well as mentioning Apache Mina SSHD as a
potential way forward in the future. Please feel free to edit the answer if I
got anything wrong, and/or correct me here on this comment thread.
> Deprecate Wagon SSH Provider
> ----------------------------
>
> Key: WAGON-616
> URL: https://issues.apache.org/jira/browse/WAGON-616
> Project: Maven Wagon
> Issue Type: Task
> Components: wagon-ssh
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 3.5.0
>
>
> This provider has serious implications and implementation issues:
> - JSch http://www.jcraft.com/jsch/ failed to provide a source repository,
> accept contributions and address issues.
> - Too complex and low level.
> - It is disputed whether this is open source at all.
> The sshexe ({{scp}}) provider remains until someone wants to write something
> on top of Apache MINA SSHD.
> We are deprecating this provider to be removed in 4.0.0.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
