[
https://issues.apache.org/jira/browse/WAGON-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495720#comment-17495720
]
Michael Osipov edited comment on WAGON-616 at 4/3/22 10:54 AM:
---------------------------------------------------------------
Provider:
https://maven.apache.org/wagon/wagon-providers/wagon-ssh-external/index.html
Additionally to the issues in the description: I have been the sole maintainer
of Wagon for past four years, it requires a tremendous amount of time to
understand issues and properly fix them. Given that millions use it and almost
no one aids me, it pushes me into a position that it simply makes no sense to
support multiple providers for the same protocol if there is virtually no
benefit. SSH is here to stay, for whatever reasons you are using it. The
OpenBSD team supports OpenSSH, we wrap it. Minimal effort. Given that a rewrite
to Apache MINA will require a lot of time, I won't do unless someone is willing
to pay for it. Most of the discussions happened internally that we don't want
to support multiple routes and need to minimize our effort. We also have this:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup
was (Author: michael-o):
Provider:
https://maven.apache.org/wagon/wagon-providers/wagon-ssh-external/index.html
Additionally to the issues in the description: I have been the sole maintainer
of Wagon for past four years, it requires a tremendous amount of time to
understand issues and properly fix them. Given that millions use it and almost
no one aids me, it pushes me into a position that it simply makes no sense to
support multiple providers for the same protocol if there is virtually no
benefit. SSH is here to stay, for whatehver reasons you are using it. The
OpenBSD team supports OpenSSH, we wrap it. Minimal effort. Given that a rewrite
to Apache MINA will require a lot of time, I won't do unless someone is willing
to pay for it. Most of the discussions happened internally that we don't want
to support multiple routes and need to minimize our effort. We also have this:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup
> 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)
