jgit/org.eclipse.jgit.ssh.jsch
Matthias Sohn ff20da9b89 Enable using slf4j 2.x
Eclipse platform moved to sfl4j 2.x. Hence relax version constraint so
that both 1.7 and 2.x are allowed.

Bug: egit-5
Change-Id: Ie0b00310d8f3f2553457c8668a38978a67b8febe
2023-12-22 23:20:41 +01:00
..
.settings Fix all Javadoc warnings and fail on them 2023-06-16 01:08:13 +02:00
META-INF Enable using slf4j 2.x 2023-12-22 23:20:41 +01:00
OSGI-INF/l10n OSGi: move plugin localization to subdirectory 2023-09-12 20:27:59 +02:00
resources Fix the path for JSchText.properties 2022-11-07 09:20:49 -05:00
src/org/eclipse/jgit [errorprone] Add missing javadoc summary 2023-09-25 22:06:13 +02:00
.classpath Bump minimum required Java version to 11 2021-09-29 17:12:12 +02:00
.fbprefs Decouple JSch from JGit Core 2020-06-01 01:46:59 +02:00
.gitignore Decouple JSch from JGit Core 2020-06-01 01:46:59 +02:00
.project Decouple JSch from JGit Core 2020-06-01 01:46:59 +02:00
BUILD Decouple JSch from JGit Core 2020-06-01 01:46:59 +02:00
README.md Typo fix in o.e.j.ssh.{jsch,apache}/README.md 2021-11-15 22:26:21 +01:00
about.html Decouple JSch from JGit Core 2020-06-01 01:46:59 +02:00
build.properties OSGi: move plugin localization to subdirectory 2023-09-12 20:27:59 +02:00
pom.xml Prepare 6.9.0-SNAPSHOT builds 2023-12-04 23:02:44 +01:00

README.md

JGit SSH support via JSch

This bundle provides an implementation of git transport over SSH implemented via JSch.

This bundle should be considered deprecated. It is essentially unmaintained, and the JGit project may decide anytime to remove it completely without further ado.

The officially supported SSH transport is in bundle org.eclipse.jgit.ssh.apache and is built upon Apache MINA sshd.

Service registration

This bundle declares a service for the java.util.ServiceLoader for interface org.eclipse.jgit.transport.ssh.SshSessionFactory. The core JGit bundle uses the service loader to pick up an implementation of that interface. The bundle in an OSGi fragment to ensure that the service loader works in an OSGi environment without the need to install a service loader bridge.

Note that JGit simply uses the first SshSessionFactory provided by the ServiceLoader.

Using a different SSH implementation

To use a different SSH implementation:

  • Do not include this bundle in your product.
  • Include the bundle of the alternate implementation.
    • If the service loader finds the alternate implementation, nothing more is needed.
    • Otherwise ensure the service declaration from the other bundle is on the Classpath of bundle org.eclipse.jgit,
    • or set the SshSessionFactory for JGit explicitly (see below).

Configuring an SSH implementation for JGit

The simplest way to set an SSH implementation for JGit is to install it globally via SshSessionFactory.setInstance(). This instance will be used by JGit for all SSH connections by default.

It is also possible to set the SSH implementation individually for any git command that needs a transport (TransportCommand) via a org.eclipse.jgit.api.TransportConfigCallback.

To do so, set the wanted SshSessionFactory on the SSH transport, like:

SshSessionFactory customFactory = ...; // Get it from wherever
FetchCommand fetch = git.fetch()
  .setTransportConfigCallback(transport -> {
    if (transport instanceof SshTransport) {
      ((SshTransport) transport).setSshSessionFactory(customFactory);
    }
  })
  ...
  .call();

Using an external SSH executable

JGit has built-in support for not using any Java SSH implementation but an external SSH executable. To use an external SSH executable, set environment variable GIT_SSH to the path of the executable. JGit will create a sub-process to run the executable and communicate with this sub-process to perform the git operation.