Distributed Version Management Suggestions in Eclipse

Question

We are a small software company that has been using CVS and SVN for version control (and Eclipse for writing code) for about 10 years. Now we are considering switching some of our projects to using a distributed version control system.

We want to use something like git, mercurial, etc. But - and here's the key - our new system should work well with Eclipse. CVS and SVN are tightly integrated with Eclipse (via plugins such as Subclipse), so any new version control system we are switching to will need to have their own plugins that comply with this standard.

Is there anything similar?

Answer 1

Eclipse is tied to Git since Alblue puts it last year :

At this point, the future of Eclipse and DVCS rests with eGit, whether it is good or not. It is very likely that Eclipse 3.6 will have eGit support by default; and it is based on the same JGit library that NetBeans will use to implement NetBeans, so at least it can be updated.

There was a long discussion about the merits of various DVCS on Eclipse bug 257706 , and the final result was for Git as the future DVCS for Eclipse, and not other DVCS.

You will find the first tutorial in this EclipseCon2010 presentation .
And a more detailed page in the Eclipse wiki .

You can see both Mercurial and Git in action in Eclipse in those Ekke .

vs.

Ekke's ending at that time (March 2010) was a good overview of where the two DVCS tools stand with Eclipse:

You may ask: why Mercurial? Didn't you know that sooner or later Eclipse projects will use EGit / JGit?
Yes. I know, and of course I use EGit to access Eclipse projects.
But I was looking for a solution that works now, and a solution to the needs of our work processes. When working with DVCS, you get more freedom how to organize and use your repositories, where you can easily navigate between them. This is not always easy to solve, but the tool you use should be.

I really appreciate the hard work of the EGit / JGit team in recent months, and much remains to be done before the Helios release.
Thanks for fixing the bugs, and I support you with testing and reporting issues. Perhaps in a few months the world looks different - there are ways to convert hg to Git http://hg-git.github.com/ or quick export. I am trying to use this converter - projects after EclipseCon to provide redViews and red sources, as well as Git Repositories.

Answer 2

A plugin exists for Git, Lookup EGit from a software update tool. However, it is still in incubation, so I do not comment on how stable it is. It seems still good.

Answer 3

Our team has been converted from svn to git, but currently it is not so tightly integrated. We prefer the CLI for it, not for gui at all. I suppose this will improve in the future, but at the moment this may be a moot point. We are all very pleased with git, although we are happy to use it.