MercurialEclipse on Windows 7 64bit: doesn't install "Windows Binaries for Mercurial"

set up my machine at work (WXP 32bit) and MercurialEclipse in Eclipse Helios from market place worked without problems.

At home I did the same procedure but on W7Pro 64bit. MercurialEclipse itself got installed, but it errored out upon Workspace restart that the hg command was not found; and it's true, there was none installed.

Comparing the plugin configurations within both Eclipse installations I discovered that W7Pro 64bit misses the Windows Binaries for Mercurial plugin. Is that architecture dependent? Is there a way to fix this?

Update:

I verified with multiple installations: MercurialEclipse requires an external binary to properly work. I was confused because through testing on my first installation I also installed the Windows Binaries for Mercurial "somehow". On my second machine I didn't and I also hadn't installed MercurialHg.

By default MercurialEclipse simple requires hg in its configuration which implicitly assumes the binary must be available in the path somewhere. The Windows Binaries for Mercurial works a bit different, it installs a private copy of hg.exe ins开发者_开发百科ide the eclipse/ folder somewhere and sets the absolute path in the MercurialEclipse configuration. Both ways work equally (ignoring differences which could be arise due version differences), since either installation would use your mercurial.ini from your home directory.

---

You should be able to pick up a copy of the hg (Mercurial) binaries from here.

---

You are absolutely right; MercurialEclipse delegates control to the hg CLI. This has recently changed with 2.0, which uses JavaHg (which is a Java interface over the Mercurial command server).

I have never used the Windows Binaries for Mercurial. My Windows setup comprises TortoiseHg (choose the latest 32-bit or 64-bit release based on your supported platform), Eclipse (choose the latest 32-bit or 64-bit release based on your supported platform) and MercurialEclipse (I have version 1.9.4.201203270141; I am yet to try 2.0.0, which was released a few hours ago)