What's the relationship between the two MercurialEclipse plugin sites?

Question

What are the similarities and differences in functionality and project leadership between the two MercurialEclipse plugins that are currently (November 2012) available in the Eclipse Marketplace?

Just to expand on the question a bit:

I just want to use the working copy of a Mercurial project within Eclipse, but when I look for a Mercurial plugin I face this confusing choice. I suspect that for the moment it doesn't matter very much which I use. But of course I don't know that for certain.

At present (November 2012), there's a MercurialEclipse listed among products on Intland Software's web site, present in the Eclipse Marketplace as "MercurialEclipse (was: HgEclipse)", with a home page at JavaForge.com. There's another MercurialEclipse in the Eclipse Marketplace as "MercurialEclipse" that is more popular by downloads since August and that has a home page at BitBucket.org.

I see that there's shared history, but at present, looking at JavaForge and BitBucket, they list different version numbers (1.9.1 and 2.0.1 respectively) and different Eclipse update sites. I see that the codebase has diverged and reunited before (http://andrei.gmxhome.de/mercurialeclipse/index.html). Do we now have two sites for two stages in the same line of development? Or is there perhaps a rivalry (whether intentional or unintentional) in which I'll have to choose a side? In that case, does someone here have at hand the relevant information for choosing?

Vertebrate

I noticed this answer that is relevant, but not quite definitive: https://mcmap.net/q/1317450/-what-is-the-official-active-home-of-the-mercurialeclipse-plugin – Vertebrate

Answer 1

The short answer is they are the same with the Javaforge site lagging behind the Bitbucket site in releases. All bugs should be files on the Bitbucket site: https://bitbucket.org/mercurialeclipse/main

Originally MercurialEclipse was hosted on Bitbucket. Around the 1.5 release if I remember correctly Intland forked it to Javaforge. This is where the name HgEclipse originated. After some time the project reunited on Javaforge. Some time later just before the 2.0 release the project moved back to Bitbucket. There are a few reasons for moving back to bitbucket. One of them being that Intland did not do releases promptly and this caused confusion with users. Another reason is the JavaHg is hosted on Bitbucket and Bitbucket is otherwise a nice host.

Even though Intland has not directly contributed in a while I think they are still interested in hosting releases. Their update site includes Mercurial binaries whereas the Bitbucket one currently doesn't.

Pili

SO the one on Javaforge is old? – Inessa

Thats correct. As of today the javaforge update site has a build from october of last year. – Pili

I'm very confused, there seems to be multiple locations including the eclipse market to get it (there are two called the same thing in the market). ALl I really need is the m2e SCM integration. – Inessa

In the Eclipse marketplace use the one with 2.1 version posted by me - that is the same as the bitbucket one (which is also the same as this one code.google.com/a/eclipselabs.org/p/mercurialeclipse ). Unfortunately as far as I know m2e SCM integration is not implemented. – Pili

Its a vital component for those that use the plugin, which is likely a lot of people. In the mean time I found a way to do it via import, which seemed to handle the modules well enough. – Inessa