Go to file
David Turner 6b1e3c58b1 Run auto GC in the background
When running an automatic GC on a FileRepository, when the caller
passes a NullProgressMonitor, run the GC in a background thread. Use a
thread pool of size 1 to limit the number of background threads spawned
for background gc in the same application. In the next minor release we
can make the thread pool configurable.

In some cases, the auto GC limit is lower than the true number of
unreachable loose objects, so auto GC will run after every (e.g) fetch
operation.  This leads to the appearance of poor fetch performance.
Since these GCs will never make progress (until either the objects
become referenced, or the two week timeout expires), blocking on them
simply reduces throughput.

In the event that an auto GC would make progress, it's still OK if it
runs in the background. The progress will still happen.

This matches the behavior of regular git.

Git (and now jgit) uses the lock file for gc.log to prevent simultaneous
runs of background gc. Further, it writes errors to gc.log, and won't
run background gc if that file is present and recent. If gc.log is too
old (according to the config gc.logexpiry), it will be ignored.

Change-Id: I3870cadb4a0a6763feff252e6eaef99f4aa8d0df
Signed-off-by: David Turner <dturner@twosigma.com>
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
2017-06-06 01:18:29 +02:00
.mvn Configure max heap size for Maven build 2016-12-09 11:02:10 +01:00
lib bazel: Consume hamcrest through transitive dependency 2017-03-23 06:47:49 +01:00
org.eclipse.jgit Run auto GC in the background 2017-06-06 01:18:29 +02:00
org.eclipse.jgit.ant Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.ant.test Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.archive Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.http.apache Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.http.server Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.http.test Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.junit Run auto GC in the background 2017-06-06 01:18:29 +02:00
org.eclipse.jgit.junit.http Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.lfs Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.lfs.server Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.lfs.server.test Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.lfs.test Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.packaging Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.pgm Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
org.eclipse.jgit.pgm.test Run auto GC in the background 2017-06-06 01:18:29 +02:00
org.eclipse.jgit.test Cleanup and test trailing slash handling in ManifestParser 2017-04-11 00:37:38 +02:00
org.eclipse.jgit.ui Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00
tools Implement initial framework of Bazel build 2017-01-18 19:13:16 -04:00
.gitattributes Initial JGit contribution to eclipse.org 2009-09-29 16:47:03 -07:00
.gitignore Remove Buck build 2017-03-22 01:41:21 +01:00
.mailmap Update .mailmap 2017-02-13 10:19:56 +09:00
BUILD Add remaining parts of the bazel build 2017-03-21 09:24:12 +01:00
CONTRIBUTING.md Update SUBMITTING_PATCHES 2014-07-20 17:44:53 -04:00
LICENSE Clean up LICENSE file 2010-07-02 14:52:49 -07:00
README.md Update minimum JDK version in README 2017-02-10 18:47:39 -04:00
WORKSPACE Downgrade Jetty to 9.3.17.v20170317 in Bazel build 2017-04-03 08:33:33 +09:00
pom.xml Prepare 4.7.1-SNAPSHOT 2017-04-06 00:16:53 +02:00

README.md

Java Git

An implementation of the Git version control system in pure Java.

This package is licensed under the EDL (Eclipse Distribution License).

JGit can be imported straight into Eclipse, built and tested from there, but the automated builds use Maven.

  • org.eclipse.jgit

    A pure Java library capable of being run standalone, with no additional support libraries. It provides classes to read and write a Git repository and operate on a working directory.

    All portions of JGit are covered by the EDL. Absolutely no GPL, LGPL or EPL contributions are accepted within this package.

  • org.eclipse.jgit.ant

    Ant tasks based on JGit.

  • org.eclipse.jgit.archive

    Support for exporting to various archive formats (zip etc).

  • org.eclipse.jgit.http.apache

    Apache httpclient support

  • org.eclipse.jgit.http.server

    Server for the smart and dumb Git HTTP protocol.

  • org.eclipse.jgit.pgm

    Command-line interface Git commands implemented using JGit ("pgm" stands for program).

  • org.eclipse.jgit.packaging

    Production of Eclipse features and p2 repository for JGit. See the JGit Wiki on why and how to use this module.

Tests

  • org.eclipse.jgit.junit

    Helpers for unit testing

  • org.eclipse.jgit.test

    Unit tests for org.eclipse.jgit

  • org.eclipse.jgit.ant.test

  • org.eclipse.jgit.pgm.test

  • org.eclipse.jgit.http.test

  • org.eclipse.jgit.junit.test

    No further description needed

Warnings/Caveats

  • Native smbolic links are supported, provided the file system supports them. For Windows you must have Windows Vista/Windows 2008 or newer, use a non-administrator account and have the SeCreateSymbolicLinkPrivilege.

  • Only the timestamp of the index is used by jgit if the index is dirty.

  • JGit requires at least a Java 8 JDK.

  • CRLF conversion is performed depending on the core.autocrlf setting, however Git for Windows by default stores that setting during installation in the "system wide" configuration file. If Git is not installed, use the global or repository configuration for the core.autocrlf setting.

  • The system wide configuration file is located relative to where C Git is installed. Make sure Git can be found via the PATH environment variable. When installing Git for Windows check the "Run Git from the Windows Command Prompt" option. There are other options like Eclipse settings that can be used for pointing out where C Git is installed. Modifying PATH is the recommended option if C Git is installed.

  • We try to use the same notation of $HOME as C Git does. On Windows this is often not the same value as the user.home system property.

Package Features

  • org.eclipse.jgit/

    • Read loose and packed commits, trees, blobs, including deltafied objects.

    • Read objects from shared repositories

    • Write loose commits, trees, blobs.

    • Write blobs from local files or Java InputStreams.

    • Read blobs as Java InputStreams.

    • Copy trees to local directory, or local directory to a tree.

    • Lazily loads objects as necessary.

    • Read and write .git/config files.

    • Create a new repository.

    • Read and write refs, including walking through symrefs.

    • Read, update and write the Git index.

    • Checkout in dirty working directory if trivial.

    • Walk the history from a given set of commits looking for commits introducing changes in files under a specified path.

    • Object transport Fetch via ssh, git, http, Amazon S3 and bundles. Push via ssh, git and Amazon S3. JGit does not yet deltify the pushed packs so they may be a lot larger than C Git packs.

    • Garbage collection

    • Merge

    • Rebase

    • And much more

  • org.eclipse.jgit.pgm/

    • Assorted set of command line utilities. Mostly for ad-hoc testing of jgit log, glog, fetch etc.
  • org.eclipse.jgit.ant/

    • Ant tasks
  • org.eclipse.jgit.archive/

    • Support for Zip/Tar and other formats
  • org.eclipse.http.*/

    • HTTP client and server support

Missing Features

There are some missing features:

  • gitattributes support

Support

Post question, comments or patches to the jgit-dev@eclipse.org mailing list. You need to be subscribed to post, see here:

https://dev.eclipse.org/mailman/listinfo/jgit-dev

Contributing

See the EGit Contributor Guide:

http://wiki.eclipse.org/EGit/Contributor_Guide

About Git

More information about Git, its repository format, and the canonical C based implementation can be obtained from the Git website:

http://git-scm.com/