jgit.git - JGit, the Java implementation of git: https://github.com/eclipse-jgit/jgit

	Commit message (Collapse)	Author	Age	Files	Lines
*	Avoid warning "no explicit project encoding"	Michael Keppler	2022-05-26	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \|	Eclipse 2022-06 raises that warning for each project without explicit encoding. We can avoid the warning by adding explicit project settings for the otherwise implicit encoding. There is no functional change, neither for users of Eclipse nor for users of other IDEs or build tools. Signed-off-by: Michael Keppler <Michael.Keppler@gmx.de> Change-Id: I30a6f1369ef09bd445f5730628d01772db2ee7b3
*	Decouple JSch from JGit Core	Matthias Sohn	2020-06-01	4	-0/+11
	Motivation: JSch serves as 'default' implementations of the SSH transport. If a client application does not use it then there is no need to pull in this dependency. Move the classes depending on JSch to an OSGi fragment extending the org.eclipse.jgit bundle and keep them in the same package as before since moving them to another package would break API. Defer moving them to a separate package to the next major release. Add a new feature org.eclipse.jgit.ssh.jsch feature to enable installation. With that users can now decide which of the ssh client integrations (JCraft JSch or Apache Mina SSHD) they want to install. We will remove the JCraft JSch integration in a later step due to the reasons discussed in bug 520927. Bug: 553625 Change-Id: I5979c8a9dbbe878a2e8ac0fbfde7230059d74dc2 Also-by: Michael Dardis <git@md-5.net> Signed-off-by: Michael Dardis <git@md-5.net> Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Signed-off-by: David Ostrovsky <david@ostrovsky.org>