How stable is the git plugin for eclipse?
I was intending to have a play with git, and was wondering if anyone had used the git plugin for eclipse
I see it's at version 0.3.1, and was wondering if anyone knew how stable it was / any gotchas?
Update:
If you are using a recent version of Eclipse, your Help menu has an 'Eclipse Marketplace...' link.
Enter 'git' in the Find field. This shows me EGit.
This is also very high in the Popular plugins list.
Click install. Much easier than having to add update site locations by hand.
Solution 1:
Github blog spoke yesterday about Egit plugin:
http://freshmeat.net/projects/jgit/
Solution 2:
I'm using if for day-to-day work and I find it stable. Lately the plugin has made good progress and has added:
- merge support, including a in-Eclipse merge tool;
- a basic synchronise view;
- reading of .git/info/exclude and .gitignore files.
- rebasing;
- streamlined commands for pushing and pulling;
- cherry-picking.
Be sure to skim the EGit User Guide for a good overview of the current functionality.
I find that I only need to drop to the comand line for interactive rebases.
As an official Eclipse project I am confident that EGit will receive all the main features of the command-line client.
Solution 3:
EGit is still in eclipse incubation. You can install it using the Eclipse update manager.
- Select Help -> Install New Software...
- You probably do not have the JGit update URL in your list of sites so in the 'Work with:' field enter this url: http://www.jgit.org/updates
- Click Add...
- You should now see Eclipse Git Plugin - Integration Build (Incubation) listed as available software to install. Check it and click Next.
- Click Next and agree to the license and it should be installed.
Solution 4:
You can integrate Git-GUI with Eclipse as an alternative to EGit.
See this two part YouTube tutorial specific to Windows:
http://www.youtube.com/watch?v=DcM1xOiaidk
http://www.youtube.com/watch?v=1OrPJClD92s
Solution 5:
It still seems barely usable, to tell the truth, especially in comparison to the CVS and SVN plugins. Is it really GIT so different that developer with four years of CVS and SVN plugin experience should be completely lost with completely different GUI, unheard commands, two or even single word error messages and "features" like overwriting the shared repository without warning? Do not use it, use command line interface. If you do not like command line interface, do not use GIT at all.