This repository only contains a single initial commit from Feb 12, 2011 and the content does not match the source code included in the latest release's zip archive http://sourceforge.net/projects/jsch/files/jsch/0.1.54/jsch-0.1.54.zip/download
So this repository does not have the source code version used to build the latest release 0.1.54. The CQ for jsch 0.1.54 [5] references the source archive available on Maven central. [5] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12480 On Thu, Nov 16, 2017 at 1:04 AM, Joakim Erdfelt <joakim.erdf...@gmail.com> wrote: > The official repo appears to be http://git.jcraft.com/jsch.git > > I found it referenced in the official zip file release: jsch-0.1.54.zip > > However, that git repo also has no test cases. > > - Joakim Erdfelt > > > On Wed, Nov 15, 2017 at 4:43 PM, Matthias Sohn <matthias.s...@gmail.com> > wrote: > >> Forking jsch is hard until we can find its source code repository. >> The download archive available on [1] contains source code but no tests >> :-( >> Same problem with the source archive available on Maven central [2]. >> Also see this post on the Jsch mailing list [3]. >> >> It seems sshj [4] and mina-sshd are more active and at least sshj is not >> a one man show. >> mina-sshd is also mostly implemented by a single developer. Its sshd >> daemon is used in Gerrit. >> >> Will need to compare APIs and implemented features. >> >> [1] http://www.jcraft.com/jsch/ >> [2] http://repo1.maven.org/maven2/com/jcraft/jsch/0.1.54/ >> [3] https://sourceforge.net/p/jsch/mailman/jsch-users/?viewmonth >> =201711&viewday=13 >> [4] https://github.com/hierynomus/sshj >> >> -Matthias >> >> On Wed, Nov 15, 2017 at 5:25 PM, Doug Schaefer <dschae...@blackberry.com> >> wrote: >> >>> 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, http://guw.io/ >>> >>> >>> >>> >>> >>> >>> >>> >>> On Nov 15, 2017, at 08:02, Matthias Sohn <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 >>> 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 >>> >> >> >> _______________________________________________ >> 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 >> > > > _______________________________________________ > 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 >
_______________________________________________ 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
