[Javagit-devel] rewritten FAQ #10

[Ross S. <ros...@ny...>]

I rewrote Question #10 in the FAQ (How is JavaGit different from JGit/ 
EGit?) - anyone have any comments?  I committed this, but didn't  
publish.
=====================
JGit is a pure Java implementation of a git client, developed in  
tandem with EGit, an Eclipse plugin for git. While JGit is mature,  
full-featured, and flexible, it does have a few drawbacks:

1. Documentation for JGit is sparse. For a developer, using it for a  
project would mean spending time combing through JGit source;  
ideally, we wanted an API where a .jar, the JavaDocs, and an  
introductory HOWTO would be sufficient.

2. It's bound to a pure Java implementation of git functionality. We  
aimed for an architecture where, if we should later want to hook into  
native git C (using JNI or some other Java/C bridge), or even provide  
pure Java implementations, we could do so with no public-facing API  
impact.

3. JGit is tied on some level to EGit. We'd like to provide a library  
that's designed to stand on its own from day one.

After some consideration, we decided to create our own git API,  
intended to address the above concerns.  We're not trying to take  
away from JGit - it's far more feature-rich than JavaGit at present.   
But competition is a good thing, and we hope to bridge that feature gap.