mercurial gpl license prevents adoption at eclipse.org ?

[Peter Arrenbrecht]

On Tue, Apr 14, 2009 at 7:24 PM, David Ripton <dripton at ripton.net> wrote:
> On 2009.04.14 18:42:03 +0200, Masklinn wrote:
>> On 13 Apr 2009, at 18:00 , rupert.thurner wrote:
>> > the problem is the mercurial license, or jythons as well?
>> >
>>
>> As MPM said, it's Eclipse's. And the problem was exactly the same with
>> Git, which lead to a complete reimplementation of Git in java (that's
>> jgit) specifically for the purpose of building an Eclipse plugin on
>> top of *that*.
>
>> So if you want to have a Mercurial plugin that ships with eclipse, I'd
>> guess you'll have to do the same thing: reimplement mercurial in java
>> using a license compatible with with their EPL, and implement a plugin
>> on top of *that* (or adapt the egit plugin).
>
> Another option would be to not embed Mercurial into the Eclipse process,
> but instead to fork off a subprocess and call hg though its documented
> public command-line interface, then check return codes and parse stdout
> and stderr.
>
> Not much fun, and not necessarily super-high-performance, but easy and
> legal.

And being done already:

  http://www.vectrace.com/mercurialeclipse
  http://www.goldenhammers.com/merclipse

-parren