From: Shawn Pearce <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Java GIT/Eclipse GIT version 0.1.1
Date: Fri, 28 Jul 2006 02:36:20 -0400 [thread overview]
Message-ID: <20060728063620.GD30783@spearce.org> (raw)
My Java GIT library and Eclipse GIT team provider is now at a point
where it may be partially useful to someone else who is also trying
to write something which interacts with GIT. Or who might also
be interested in seeing a pure-Java Eclipse team provider for GIT.
So I've posted my repository (currently ~200 KB) on my website:
http://www.spearce.org/projects/scm/egit.git
The underlying Java library is fairly functional and can read and
write a repository. Creating a series of Ant tasks for use in an
automated build environment would probably be pretty trivial with
this library.
The Eclipse plugin can't commit. Or do a lot of other really
useful things. So its not end-user ready. :-)
The code is licensed under the Apache License, version 2.0.
I would appreciate any and all input, feedback, etc. that anyone
might have on this library or plugin. Patches are of course
certainly welcome. :-)
For what its worth I'm trying to keep this library and Eclipse
plugin 100% pure Java and avoid calling out to the canonical C
implementation of GIT. However I have no plans to implement the
delta packing algorithm used by git-pack-objects. Consequently if
this code ever produces packs it will be strictly zlib deflated
objects without delta compression.
--
Shawn.
next reply other threads:[~2006-07-28 6:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 6:36 Shawn Pearce [this message]
2006-07-28 6:49 ` Java GIT/Eclipse GIT version 0.1.1 Peter Baumann
2006-07-28 7:08 ` Pavel Roskin
2006-07-28 7:23 ` Peter Baumann
2006-07-29 2:10 ` Pavel Roskin
2006-07-29 16:46 ` Peter Baumann
2006-07-29 3:32 ` Shawn Pearce
2006-07-29 3:55 ` Pavel Roskin
2006-07-29 4:08 ` Shawn Pearce
2006-07-29 10:15 ` Jakub Narebski
2006-07-30 14:55 ` Daniel Barkalow
2006-07-31 4:22 ` Shawn Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060728063620.GD30783@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.