Re: Any news on an Eclipse plugin?

From: Shawn Pearce <spearce@spearce.org>
Date: Mar 13, 2006, 04:09 UTC
Message-ID: <20060313040924.GB17901@spearce.org>
In-Reply-To: <44147B8B.4050503@cc.jyu.fi>

lamikr <lamikr@cc.jyu.fi> wrote:

Show 6 quoted lines

> Have you yet made any kind of planning of the features that would be
> available or put up the repository?
> I use novadays Eclipse basically for all of my editing and something
> like CVS/Subclipse plug-ins for git would be cool.
> (cdt cross-indexing is still a little bit slow with the amount of files
> in kernel so with kernel I have turned that off)

Right now I'm just trying to get the basic Eclipse team plugin plumbing into place. For my first `release' however I am planning on implementing the following:

1) read the HEAD tree-ish into an in-memory index within Eclipse from
   loose objects only
2) add files/subtrees to that tree
3) delete files/subtrees from that tree
4) commit the modified tree as a single parent commit
5) update HEAD with the new commit

But that's actually a lot of work.  :-)

There's a lot of really critical stuff not in that list:

6) reading objects from packs
7) pulling or pushing from a remote
8) merges and multi-parent commits
9) synchronization of the workspace with the native git 'index' file
... plus lots of other useful things ...

I'm working on that first list (1-5) this week and will post
a complete repository as soon as I have that working such that
another Eclipse developer might be able to do something with it.
Then I'll likely start in on 6 and 7 and be forced to deal with
8 when 7 is doing pulls in an interesting way.  That's certainly
weeks away from being remotely useful.

Show 16 quoted lines

> Noel Grandin wrote:
> >The subversion plugin (subclipse.tigris.org) might be a good starting
> >point since it delegates a lot of it's low-level work through an
> >interface called svnClientAdapter. Re-implementing that to talk to git
> >should get you something useful in a reasonable time-frame.
> >
> >Note that an eclipse team plugin is a pretty complicated beast.
>
>
> Yes, but very powerfull for the people like me who have who just have
> never bothered to learn VI/Emacs/sed properly
> and feel with them like having 5 thumps, code finders, search tools,
> refactoring tools, etc. available in Eclipse are very cool.
> 
> So if the repository for git plug-ins goes up somewhere I could try to
> help a little bit.

The more the merrier. As has been pointed out an Eclipse team plugin is not a trivial chunk of code.

As a side effect of this effort I'd also like to see a set of Ant tasks written. I'm building a non-Eclipse specific GIT API in pure Java to provide implementation to the Eclipse plugins. Some functions are likely going to just fork/exec the core GIT tools as I'm not planning on implementing pack deltification or rename tracking in Java.

Anyhoo - if you are still interested in this project look for an email from me later this week. I should have a repository available then.

-- 
Shawn.