Let's clarify this before this gets out of hand.
For EGit the plan is indeed to switch the default at
some point and use Apache MINA sshd exclusively.
I hope a lot of the code developed now for JGit can
eventually be moved there.
For the JGit command-line tools using Apache MINA
sshd exclusively is an option, but
for now, JSch is still the default. Don't know if we
want to switch.
For the JGit core library, I had *not* planned to
replace JSch with Apache MINA anytime soon.
JGit is a library, and its users may use different
versions of Apache MINA sshd (like Gerrit) or,
like Randall points out, not have the ability to use
Apache MINA sshd at all.
Such concerns were the reason why I did this all in
a completely separate bundle that
people may use or not.
Cheers,
Thomas
Thomas,
Apache Mina SSHD is not available on the HPE NonStop
platform to my
knowledge. My team is generally responsible for ports,
and I would have
heard about this one being done. So it's not a
capability issue between the
two, it is an availability issue.
Randall
-----Original
Message-----
From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Sent: November 18, 2018 12:43
To: Randall S. Becker <rsbecker@xxxxxxxxxxxxx>
Cc: Thomas Wolf <thomas.wolf@xxxxxxxxxx>;
EGit developer discussion
<egit-dev@xxxxxxxxxxx>;
JGit Developers list <jgit-dev@xxxxxxxxxxx>
Subject: Re: [egit-dev] Bug 520927: moving away from
JSch
Randall,
On Nov 18, 2018, at
18:32, Randall S. Becker <rsbecker@xxxxxxxxxxxxx>
wrote:
From a headless perspective, JGit is used on
platforms that do not
support either EGit or the specific sshd
implementation being integrated
here.
Can you clarify the specific limitations around Apache
Mina SSHD in
comparison to JSch?
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/
_______________________________________________
jgit-dev mailing list
jgit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jgit-dev