What is the relationship between the two MercurialEclipse plugins?

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

To talk a little about the question:

I just want to use a working copy of the Mercurial project in Eclipse, but when I look for the Mercurial plugin, I come across this confused choice. I suspect that at the moment it does not really matter what I use. But, of course, I don’t know for sure.

Currently (November 2012), MercurialEclipse has listed among the products on the Intland Software website represented on the Eclipse Marketplace as “MercurialEclipse (was: HgEclipse),” with a homepage on JavaForge.com. There's also a MercurialEclipse in the Eclipse Marketplace as the "MercurialEclipse", which is more popular on download since August, and it has a homepage on BitBucket.org.

I see that there is a common story, but currently, 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 code base has diverged and reunited earlier ( http://andrei.gmxhome.de/mercurialeclipse/index.html ). We now have two sites for two stages in the same line of development? Or maybe there is rivalry (intentional or unintentional) in which I have to choose a side? In this case, does someone here have the right information to choose from?

+8
eclipse mercurial mercurialeclipse
source share
1 answer

Short answer: they are the same with the Javaforge site, which is behind the Bitbucket site in releases. All errors must be files on the Bitbucket website: https://bitbucket.org/mercurialeclipse/main

Originally, MercurialEclipse was hosted on Bitbucket. Around release 1.5, if I remember correctly, Intland forked it in Javaforge. The name HgEclipse is called here. After some time, the project reunited with Javaforg. Some time before the release of 2.0, the project returned to Bitbucket. There are several reasons to return to the beat bag. One of them was that Intland did not release releases quickly, and this led to confusion with users. Another reason is that JavaHg is hosted on Bitbucket and Bitbucket is a great host.

Despite the fact that Intland did not directly help, I think they are still interested in posting releases. Their update site includes Mercurial binaries, while Bitbucket currently does not.

+8
source share

All Articles