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

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

[~michael-o] Thank you very much for your reply! I deeply sympathize with the 
burdens of maintainership, and I thank you from the bottom of my heart for your 
service to the open source community. I hope my message did not come across as 
accusatory or critical. I just honestly do not understand what the currently 
recommended approach is for using wagon with SSH/SCP right now. What is "the 
sshexe (scp) provider"? I tried to find it, but failed. Sorry if I'm being dumb 
here, but I am trying to maintain [my SO answer about 
wagon+SCP|https://stackoverflow.com/a/14404990/1207769], and I do not know what 
to try next. Given Maven's sparse documentation, I think SO ends up helping a 
lot of people figure out how to actually do stuff with it in practice, and I'm 
trying to be part of that solution. I just need a little guidance: a pointer to 
documentation or example somewhere?

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

Reply via email to