1 == Eclipse GIT plugin ==
3 This package is licensed under the EPL. Please refer to the COPYING
4 and LICENSE files for the complete licenses within each package.
6 This package is actually composed of three major components plus
11 An Eclipse plugin providing an interface to org.eclipse.jgit
12 and support routines to allow processing against the Eclipse
13 workspace and resource APIs, rather than the standard Java
14 file APIs. It also supplies the team provider implementation.
18 An Eclipse plugin providing the user interface on top of
19 org.eclipse.egit.core.
21 org.eclipse.egit.core.test/
23 Unit tests for org.eclipse.egit.core.
27 A plugin for packaging
29 org.eclipse.egit-feature/
31 Also packaging. This project is for building an Eclipse "feature"
32 out of the plugins above.
34 org.eclipse.egit-updatesite/
36 This package is for producing and update site, i.e. a web site
37 you can point your eclipse at and just upgrade.
39 == WARNINGS / CAVEATS ==
41 - Symbolic links are not supported because java does not support it.
42 Such links could be damaged.
44 - Only the timestamp of the index is used by jgit check if the index
47 - Don't try the plugin with a JDK other than 1.6 (Java 6) unless you
48 are prepared to investigate problems yourself. JDK 1.5.0_11 and later
49 Java 5 versions *may* work. Earlier versions do not. JDK 1.4 is *not*
50 supported. Apple's Java 1.5.0_07 is reported to work acceptably. We
51 have no information about other vendors. Please report your findings
54 - CRLF conversion is never performed. On Windows you should thereforc
55 make sure your projects and workspaces are configured to save files
56 with Unix (LF) line endings.
60 - Eclipse 3.4 is the minimum Eclipse version.
62 - Newer version of EGit may implement new functionality, remove
63 existing functions and change others without other notice than what
64 is written in the commit log and source files themselves.
67 == Package Features ==
69 org.eclipse.egit.core/
71 * Supplies an Eclipse team provider.
73 * Connect/disconnect the provider to a project.
75 * Search for the repositories associated with a project by
76 autodetecting the GIT repository directories.
78 * Store which repositories are tied to which containers in the
81 * Tracks moves/renames/deletes and reflects them in the cache
84 * Resolves through linked containers.
88 * Connect team provider wizard panels.
90 * Connect to GIT team provider by making a new repository.
92 * Connect to GIT team provider by searching local filesystem
93 for existing repository directories.
95 * Team actions: track (add), untrack (remove), disconnect, show
96 history, compare version.
98 * Resource decorator shows file/directory state in the package
99 explorer and other views.
101 * Creating new commits or amending commits.
103 * Graphical history viewer with the ability to compare versions
104 using eclipse built-in compare editor.
108 == Missing Features ==
110 There are a lot of missing features. You need the real Git for this.
111 For some operations it may just be the preferred solution also. There
112 are not just a command line, there is e.g. git-gui that makes committing
113 partial files simple.
117 - Repacking from within the plugin.
119 - Generate a GIT format patch.
121 - Apply a GIT format patch.
125 - gitattributes support
126 In particular CRLF conversion is not implemented. Files are treated
130 Submodules are not supported or even recognized.
132 - The Eclipse plugin cannot handle files outside any Eclipse project. You
133 need commit changes to such files outside of Eclipse.
137 Post question, comments or patches to the git@vger.kernel.org mailing list.
142 See SUBMITTING_PATCHES in this directory. However, feedback and bug reports
143 are also contributions.
148 More information about GIT, its repository format, and the canonical
149 C based implementation can be obtained from the GIT websites:
152 http://www.kernel.org/pub/software/scm/git/
153 http://www.kernel.org/pub/software/scm/git/docs/