[jira] [Commented] (WAGON-616) Deprecate Wagon SSH Provider

["Curtis Rueden (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WAGON-616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495080#comment-17495080 ] 

Curtis Rueden commented on WAGON-616:
-------------------------------------

The current status leaves the community rather lost in how to proceed. Comments from the maintainers would be appreciated regarding:
 * What the current recommended best practice is for transferring Maven artifacts via SSH/SCP. For example: what is "the sshexe (scp) provider"? I couldn't find it after a few web searches. Is there a guide anywhere on how to use it?
 * What about the JSch fork described in WAGON-613? Can this wagon provider not simply switch to the fork, if the upstream JSch is concerning?
 * Can you post links to discussions, e.g. mailing list threads in archives, cluing us into the rationale behind this decision, and hopefully more details on how to better move forward?

> 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)