Checking out EGit source code with EGit

Git and EGit are getting popular. In case you want to start hacking on EGit this will give you some hints.

First install EGit following this guide EGit Tutorial.

First you need a few libraries from Orbit via cvs. The cvs location is “:pserver:anonymous@dev.eclipse.org/cvsroot/tools”. You need:

  • org.eclipse.orbit/com.jcraft.jsch
  • org.eclipse.orbit/org.kohsuke.args4j
  • org.eclipse.orbit/javax.servlet

See Libraries from Orbit for getting these libraries.

Select File -> Import -> Git -> Git Repository and paste the URL “git://egit.eclipse.org/jgit.git” into the first line.

Do the same with “git://egit.eclipse.org/egit.git”.

Currently there is a little bug in EGit, please see Bug Report. If you facing the problem that the Team operations are not available on your new project my EGit Tutorial describes what to do to make the Team operations available. This should be fixed very soon, path is already commited to the master branch.

You have now the source code in your workspace and can start hacking.

For more info please see the excellent EGit Contributor Guide.

About Lars Vogel

Lars Vogel is the founder and CEO of the vogella GmbH and works as Eclipse and Android consultant, trainer and book author. He is a regular speaker at international conferences, With more than one million visitors per month his website vogella.com is one of the central sources for Eclipse and Android programming information.
This entry was posted in Eclipse and tagged , , . Bookmark the permalink.

2 Responses to Checking out EGit source code with EGit

  1. Martin Dilger says:

    Hi Lars,

    I tried your suggestions, but I’m really getting stuck at trying to import Egit-Sources into my Workspace.
    First of all, one should mention, that you are required to use Maven3 (in Alpha-Version!!) to enable
    the Build of Egit (that sucks)… But I think, this is necessary to enable the P2-Enabled build..
    When I try to import the sources I get some kind of “P2Utils cannot be resolved”.
    Any Idea on that??

  2. Lars Vogel says:

    @Martin Maven3 is not needed to check the source code. Eclipse will compile the source directly and you can test your changes in a new workbench.

Comments are closed.