That's my biggest fear depending on projects like that. And we do have a huge 
dependency on SSH communication in Eclipse, not only for EGit but the SSH 
Terminal as well and future work CDT's planning for remote builds and 
launching. Would be good to get this or something like this under our control.

Doug.

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Gunnar 
Wagenknecht
Sent: Wednesday, November 15, 2017 2:23 AM
To: Cross project issues <cross-project-issues-dev@eclipse.org>
Subject: Re: [cross-project-issues-dev] Bug tracker for Jsch

It looks like the JSch project is in a poor state.

It has been a one-developer project. The developer did not make any 
contributions on GitHub over the last year.
https://github.com/ymnk

At this point it looks like your best bet is a fork and fixing the issues 
yourself or consider migrating to a more active project.
https://github.com/hierynomus/sshj
http://mina.apache.org/sshd-project/sources.html

-Gunnar

--
Gunnar Wagenknecht
gun...@wagenknecht.org<mailto:gun...@wagenknecht.org>, http://guw.io/





On Nov 15, 2017, at 08:02, Matthias Sohn 
<matthias.s...@gmail.com<mailto:matthias.s...@gmail.com>> wrote:

Does anybody know where to report bugs for the Jsch project?

Thomas implemented several workarounds for Jsch bugs in JGit:
* "Work around a Jsch bug: ensure the user name is set from URI" [1]
* "Yet another work-around for a Jsch bug: timeouts" [2]

We would like to report these Jsch bugs to its maintainers in order to get them
fixed upstream but we struggle to find the bug tracker for Jsch. We also tried
to cc Atsuhiko Yamanaka on bug 526778 but so far we got no response.

We found this bugtracker in SourceForge [3] but aren't sure if that's correct 
since
all bugs raised there in the last years didn't get any response and the last bug
was closed back in 2013. So it looks like this bug tracker was abandoned.
I sent an email to JCraft (the company sponsoring the Jsch development) in
order to find out where we can report bugs but this email bounced.

[1]
https://git.eclipse.org/r/#/c/111359/
https://bugs.eclipse.org/bugs/show_bug.cgi?id=526778

[2]
https://git.eclipse.org/r/#/c/111421/
https://bugs.eclipse.org/bugs/show_bug.cgi?id=526867

[3] https://sourceforge.net/p/jsch/bugs/

-Matthias
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org<mailto:cross-project-issues-dev@eclipse.org>
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to