This project is a fork of the egit.git project. If you have that one already cloned locally, you can use
git clone --reference /path/to/your/egit.git/incarnation mirror_URL
to save bandwidth during cloning.
descriptionFlorian's egit tree
last changeSat, 19 Jul 2008 02:50:47 +0000 (18 22:50 -0400)
content tags
            == Java GIT and Eclipse GIT plugin ==

Parts of this package are licensed under the BSD, and others are
licensed under the EPL.  Please refer to the COPYING and LICENSE 
files for the complete licenses within each package, and please 
refer to the individual source file header to determine
which license covers it.

This package is actually composed of three major components plus
three for packaging.


    A pure Java library capable of being run standalone, with no
    additional support libraries.  Some JUnit tests are provided
    to exercise the library.  The library provides functions to
    read and write a GIT formatted repository.

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

    Unit tests for org.spearce.jgit and the same licensing rules.


    An Eclipse plugin providing an interface to org.spearce.jgit
    and support routines to allow processing against the Eclipse
    workspace and resource APIs, rather than the standard Java
    file APIs.  It also supplies the team provider implementation.
    Everything here is EPL.


    An Eclipse plugin providing the user interface on top of

    Everything here is EPL.


    Unit tests for org.spearce.egit.core.

    Everything here is EPL.


    A plugin for packaging

    Everything here is EPL.


    Also packaging. This project is for building an Eclipse "feature"
    out of the plugins above.

    Everything here is EPL.


    This package is for producing and update site, i.e. a web site
    you can point your eclipse at and just upgrade.

    Everything here is EPL.

            == WARNINGS / CAVEATS              ==

- The plugin could lockup your Eclipse workbench.  I've tried to
  make it stable and function in such a way that it can't crash
  the workbench, but that doesn't mean it won't.  :-)

- This package might eat your files.  Everything I've added to a
  repository with it has unpacked properly both with itself and
  with the canonical C based implementation, but that doesn't mean
  it won't generate a corrupt object.

- Symbolic links are not supported because java does not support it.
  Such links could be damaged.

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

- Don't try the plugin with a JDK other than 1.6 (Java 6) unless you
  are prepared to investigate problems yourself. JDK 1.5.0_11 and later
  Java 5 versions *may* work. Earlier versions do not. JDK 1.4 is *not*
  supported. Apple's Java 1.5.0_07 is reported to work acceptably. We
  have no information about other vendors. Please report your findings
  if you try.

- Do not trust this plugin to always do the right thing (yet). Please
  check with the real Git and report any problems.

            == COMPATIBILITY                   ==

- Eclipse 3.2.1 is the minimum Eclipse version. Expect this to change
  in future versions.

- Newer version of EGit/JGit may implement new functionality, remove
  existing functions and change others without other notice than what
  is written in the commit log and source files themselves.

            == Package Features                ==


    * 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.


    * Supplies an Eclipse team provider.

    * Connect/disconnect the provider to a project.

    * Search for the repositories associated with a project by
      autodecting the GIT repository directories.

    * Store which repositories are tied to which containers in the
      Eclipse workspace.

    * Tracks moves/renames/deletes and reflects them in the cache

    * Resolves through linked containers.


    * Connect team provider wizard panels.

    * Connect to GIT team provider by making a new repository.

    * Connect to GIT team provider by searching local filesystem
      for existing repository directories.

    * Team actions: track (add), untrack (remove), disconnect, show
      history, compare version.

    * Resource decorator shows file/directory state in the package
      explorer and other views.

    * Creating new commits or amending commits.

    * Graphical history viewer with the ability to compare versions
      using eclipse built-in compare editor.

            == Missing Features                ==

There are a lot of missing features. You need the real Git for this.
For some operations it may just be the preferred solution also. There
are not just a command line, there is e.g. git-gui that makes committing
partial files simple.

- GIT network protocol to pull objects from a remote repository or
  push objects to a remote repository.

- Merging. 

- Repacking from within the plugin.

- Generate a GIT format patch.

- Apply a GIT format patch.

- Documentation. :-)

- Windows support is new and very ligthly tested. Do not blame us if
  it blows, but tell us about it and what you did. Double check

- gitattributes support
  In particular CRLF conversion is not implemented. Files are treated
  as byte sequences.

- submodule support
  Submodules are not supported or even recognized.

- The Eclipse plugin cannot handle files outside any Eclipse project. You
  need commit changes to such files outside of Eclipse.

- Speed in some areas

  Java is "slooow", they say. Not true as a general statement. A lot of Java
  code is slow because it it not optimized (to some extent due to this
  belief). Java has quite good performance although it cannot compete with
  C code written by good hackers simply because C can be optimized more than
  Java when you actually do it and have the skills to do it. Some areas of
  the plugin have been optimized but not all and not conclusively. In general
  however Java almost always needs more memory than an application written in 
  e.g. C. In particular there is an overhead from the rather large standard
  libraries that a normal Java installation comes with. See the ACM report:

	Prechelt, L. 1999. Technical opinion: comparing Java vs. C/C++
        efficiency differences to interpersonal differences. Commun. ACM 42, 
        10 (Oct. 1999), 109-112. DOI=

  for an interesting comparison of C, C++ and Java. It is somewhat dated so 
  the comparison involved Java 1.2, i.e. without hotspot that appeared in Java 
  1.3 and the shared runtime in 1.4. Those features made common Java
  applications many times faster than with Java 1.2

  The conclusion from having about 30 programmers write a program to the same
  specification using their own choice of language (from C,C++ and Java) is
  that the skills of the programmer is what determines the performance of the
  code rather than choice of programming language.

  JGit is much slower (measured up to eight times for some random cases), but
  then the real Git is ridicilously fast.

            == Support                         ==

  Post question, comments or patches to the mailing list.

            == Contributing                    ==

  See SUBMITTING_PATCHES in this directory. However, feedback and bug reports
  are also contributions.

            == About GIT                       ==

More information about GIT, its repository format, and the canonical
C based implementation can be obtained from the GIT websites:
2008-07-19 Shawn O. PearceRemove support for legacy style TextBuiltinsmaster
2008-07-19 Shawn O. PearceConvert rev-list, log, glog programs to args4j
2008-07-19 Shawn O. PearceConvert tag program to args4j
2008-07-19 Shawn O. PearceConvert show-ref program to args4j
2008-07-19 Shawn O. PearceConvert push program to args4j
2008-07-19 Shawn O. PearceConvert merge-base program to args4j
2008-07-19 Shawn O. PearceConvert ls-tree program to args4j
2008-07-19 Shawn O. PearceConvert ls-remote program to args4j
2008-07-19 Shawn O. PearceConvert index-pack program to args4j
2008-07-19 Shawn O. PearceConvert fetch program to args4j
2008-07-19 Shawn O. PearceConvert diff-tree program to args4j
2008-07-19 Shawn O. PearceSupport automatic command line parsing for TextBuiltin...
2008-07-18 Shawn O. PearceConvert jgit's Main to use args4j for basic parsing...
2008-07-18 Shawn O. PearceRegister most of our OptionHandler implementations...
2008-07-18 Shawn O. PearceAdd option handler for RevTree values
2008-07-18 Shawn O. PearceAdd option handler for RevCommit values
10 years ago master
10 years ago unfinished-objects-from-arguments-patch