Re: egit/jgit wishlist

From: Shawn Pearce <spearce@spearce.org>
Date: Dec 4, 2006, 18:29 UTC
Message-ID: <20061204182902.GG6011@spearce.org>
In-Reply-To: <Pine.LNX.4.63.0612041841280.14187@alpha.polcom.net>

Grzegorz Kulewski <kangur@polcom.net> wrote:

Show 6 quoted lines

> I think that doing it in 100% pure Java is ok in long run but I wonder if 
> you couldn't make "wrapper" plugin for a start (that would call the real C 
> git for every operation) and make it usable (with full pure Java SWT UI 
> support) and then try to implement feature by feature in pure Java (with 
> config options telling what should be called by wrapper and what by pure 
> implementation)?

Several people have proposed doing exactly that, but thus far myself and Robin Rosenburg have been the only two to step forward with code. I personally want to avoid calling external programs as much as possible here, and that means staying with a 100% pure Java implementation. Hence the desire to not build a wrapper plugin.

We have the core repository reading and writing working. We can write out trees. We can create commits (we just lack UI for it). So we're part of the way there...