Difference between revisions of "EGit/FAQ"
(→What versions of Eclipse does EGit target?)
(→Where can I find older releases of EGit?)
|Line 32:||Line 32:|
! Release Version
! Release Version
! p2 repository URL
! p2 repository URL
Revision as of 17:49, 20 December 2012
|Mailing List • Forums • IRC|
|Browse Source • Project Set File|
- 1 What is Git?
- 2 What is JGit?
- 3 What is EGit?
- 4 What is New and Noteworthy?
- 5 Where can I find older releases of EGit?
- 6 What versions of Eclipse does EGit target?
- 7 What are the main differences between original Git and JGit(EGit)?
- 8 What is the mapping Git commands to EGit operations?
- 9 How compatible is EGit with Git?
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?
What is EGit?
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|
The project follows a pattern of http://download.eclipse.org/egit/updates-<release> for its sites.
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.
THIS TABLE IS CURRENTLY A DRAFT
|EGit||released for||Supported Version of Eclipse|
|2.2-SNAPSHOT||-||proposed see bug 365425 : Eclipse 3.7.2+ (Indigo)|
|126.96.36.199209190230-r||3.8.1/4.2.1 (Juno SR1)||Eclipse 3.5.2+ (Galileo) (except EGit Import Support feature, which is optional)|
|188.8.131.52206130900-r||3.8/4.2 (Juno)||Eclipse 3.5.2+ (Galileo) (except EGit Import Support feature, which is optional)|
|184.108.40.206202151440-r||3.7.2 (Indigo SR2)||Eclipse 3.5.2+ (Galileo)|
|220.127.116.11112221803-r||3.7.2 (Indigo SR2)||Eclipse 3.5.2+ (Galileo)|
|18.104.22.168109151100-r||3.7.1 (Indigo SR1)||Eclipse 3.5.2+ (Galileo)|
|22.214.171.124106090707-r||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: Compatibility is on a feature by feature basis. Currently the major version related difference is in how Git handles file names with non-ASCII file names. Git for Windows 1.7.10 and later encodes filenames in UTF-8 which is compatible with JGit. Git on Mac, v1.7.12 can encode filenames in a way that is compatible with EGit and Git for Windows if core.precomposeunicode is set to true.
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.
|core.autocrlf||Since 2.0 supports true,false and input. See the tutorial for notes about making sure EGit picks up the configuration|
|core.compression||zlib compression level|
|core.excludesfile||Contains ignore rules, in addition to .gitignore|
|core.precomposeunicode||always considered true on OS X, set on new repositories|
|core.repositoryformatversion||recognized, only "0" supported|
|core.worktree||supported in JGit, not EGit|
|diff.algorithm||myers, histogram (default: histogram)|
|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).
JGit supports some environment variables. Do not set those for the Eclipse IDE. We'll list a few ones that may be used, but most apply only to using JGit from the command line.
|GIT_CEILING_DIRECTORIES_KEY||supported. Also EGit may be benefited when used with automounted file systems|
TBD: JGit does its own parsing of the ~/.ssh/config file.