Jump to: navigation, search


< EGit
Revision as of 00:51, 10 September 2012 by Robin.rosenberg.dewire.com (Talk | contribs) (config)

Mailing ListForumsIRCmattermost
OpenHelp WantedBug Day
Browse SourceProject Set File

What is Git?

Git is a distributed SCM/VCS, which means every developer has a full copy of all history of every revision of the code, making queries against the history very fast and versatile. The EGit project is implementing Eclipse tooling on top of a Java implementation of Git.

What is JGit?

JGit is a EDL/BSD licensed, lightweight, pure Java library implementing the Git version control file access routines, network protocols, and core version control algorithms.

See the embrynonic JGitTutorial.

What is EGit?

EGit is an EPL licensed Eclipse Team provider for Git, built on top of JGit.

What is New and Noteworthy?

You can find the latest changes for EGit and JGit below:

Where can I find older releases of EGit?

It's recommended to use the latest released version of EGit, find it's p2 repository here http://download.eclipse.org/egit/updates.

In case you need an older version, try an older repository:

Release Version p2 repository URL http://download.eclipse.org/egit/updates-2.0 http://download.eclipse.org/egit/updates-1.3 http://download.eclipse.org/egit/updates-1.2 http://download.eclipse.org/egit/updates-1.1 http://download.eclipse.org/egit/updates-1.0
0.12.1 (Incubation) http://download.eclipse.org/egit/updates-0.12
0.11.3 (Incubation) http://download.eclipse.org/egit/updates-0.11
0.10.1 (Incubation) http://download.eclipse.org/egit/updates-0.10
0.9.3 (Incubation) http://download.eclipse.org/egit/updates-0.9
0.8.4 (Incubation) http://download.eclipse.org/egit/updates-0.8

The project follows a pattern of http://download.eclipse.org/egit/updates-<release> for its sites.

Retention Policy

All release p2 repositories will be kept forever.

What versions of Eclipse does EGit target?

In general EGit promises to support at least the latest two Eclipse releases.

If possible we will not prevent usage in older releases but if we want to take advantage of new functionality only available in one of the latest two Eclipse releases but not in older releases we will update dependencies which will in fact discontinue support for older releases.


EGit released for Supported Version of Eclipse
2.1-SNAPSHOT - proposed see bug 365425 : Eclipse 3.7.2+ (Indigo) 3.8/4.2 (Juno) Eclipse 3.5.2+ (Galileo) (except EGit Import Support feature, which is optional) 3.7.2 (Indigo SR2) Eclipse 3.5.2+ (Galileo) 3.7.2 (Indigo SR2) Eclipse 3.5.2+ (Galileo) 3.7.1 (Indigo SR1) Eclipse 3.5.2+ (Galileo) 3.7.0 (Indigo) Eclipse 3.5.2+ (Galileo)

Since 0.7.1 EGit requires Eclipse 3.5.2 (Galileo) or newer. See bug 308027 for more details on providing support for Eclipse 3.4.

Compatible version of Git: To Be Announced.

What are the main differences between original Git and JGit(EGit)?

See this page Differences to Git

What is the mapping Git commands to EGit operations?

See this page Mapping Git Commands

How compatible is EGit with Git?

Some, but not all configuration options on Git are available in EGit/JGit. Here is a summary, not yet complete describing some of these, including noteable differences.


config description
core.autocrlf Since 2.0 supports true,false and input. See the tutorial for notes about making sure EGit picks up the configuration
core.bare supported
core.compression zlib compression level
core.excludesfile Contains ignore rules, in addition to .gitignore
core.filemode supported
core.ignorecase not supported
core.logallrefupdates supported
core.repositoryformatversion recognized, only "0" supported
core.safecrlf not supported
core.worktree supported in JGit, not EGit
diff.algorithm "myers", "histogram" (default)
pack.indexVersion Default 2,-1 for older format

Supported in JGit, but no EGit usually amounts to having no or strange behavior would one attempt to use it in the Eclipse IDE.

Notes: For those that can read the source, look at ConfigConstants.java for a hint on what options JGit recognizes. If it appears there, an option may be supported, but it may also mean for a few cases that JGit just looks for it and then explicitly tells the user the option is not supported. If it does not appear, it's most certainly up for grabs as a contribution. The file contains lots of config options that only applies to JGit (DFS, gerrit).