From: Gabe McArthur <gabriel.mcarthur@gmail.com>
To: git@vger.kernel.org
Subject: Re: [JGIT] Request for help
Date: Fri, 4 Sep 2009 05:00:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20090904T064602-511@post.gmane.org> (raw)
In-Reply-To: 20090903155219.GI1033@spearce.org
Shawn O. Pearce <spearce <at> spearce.org> writes:
>
> Please post patches; formatted with -M. I do want to do this, I just
> don't have the patience and Maven-fu to write the new poms myself.
>
Hey,
I'm a build engineer with a considerable amount of "Maven-fu" :). I've actually
generated a patch that does everything you want (and a bit more). I'm not that
familiar with git's command line yet, so it's a bit tricky to get the patch
thing right. However, here's a rough overview of what I did:
ROOT
====
README
/bin
bash.env -- A script that you can source from Bash that
will add the 'jgit' executable and the other
scripts in this 'bin' directory to your PATH
build.sh -- A general build script, that hides some
Maven complexities for initiates.
tag.sh -- Ok, this is the only thing that will have to
be re-written. It's too tied in with git commands for
me to fully extract what it's supposed to do.
/docs
LICENSE
SUBMITTING_PATCHES
TODO
pom.xml -- A considerable amount of build logic has been
centralized here. It references 3 sub-module
projects, listed below.
/sources
/jgit-lib
pom.xml
/src/main/java....
/src/test
/java....
/resources
/exttst -- Don't know exactly where this goes, as it
doesn't seem to be doing much/being run
currently.
/jgit-pgm
pom.xml -- Does the work to do a 'jar-with-dependencies'
so that org.spearce.jgit.pgm.build can be removed.
/src/main/java....
/jgit-exec
pom.xml -- Actually generates the 'jgit' executable and
installs it in ROOT/target/bin, so that it will
be on your path after sourcing 'bin/bash.env'
/src/main/scripts/jgit
I'll try to submit a full patch later, using your conventions.
My appreciation to Shawn for pointing out this thread....
-Gabe
next prev parent reply other threads:[~2009-09-04 5:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:28 [JGIT] Request for help Nasser Grainawi
2009-09-03 0:04 ` Johannes Schindelin
2009-09-03 1:22 ` Shawn O. Pearce
2009-09-03 6:55 ` jgit diff, was " Johannes Schindelin
2009-09-03 10:45 ` [JGIT PATCH 0/5] jgit diff Johannes Schindelin
2009-09-03 10:46 ` [JGIT PATCH 1/5] Add set to IntList Johannes Schindelin
2009-09-03 10:46 ` [JGIT PATCH 2/5] Add Myers' algorithm to generate diff scripts Johannes Schindelin
2009-09-03 10:46 ` [JGIT PATCH 3/5] Add a test class for Myers' diff algorithm Johannes Schindelin
2009-09-03 10:47 ` [JGIT PATCH 4/5] Prepare RawText for diff-index and diff-files Johannes Schindelin
2009-09-03 10:47 ` [JGIT PATCH 5/5] Add the "jgit diff" command Johannes Schindelin
2009-09-03 10:48 ` [JGIT PATCH 0/5] jgit diff Johannes Schindelin
2009-10-01 18:47 ` Shawn O. Pearce
2009-10-01 21:47 ` Johannes Schindelin
2009-09-03 15:54 ` jgit diff, was Re: [JGIT] Request for help Christian Halstrick
2009-09-03 12:45 ` Jonas Fonseca
2009-09-03 14:42 ` Shawn O. Pearce
2009-09-03 15:38 ` Jonas Fonseca
2009-09-03 15:52 ` Shawn O. Pearce
2009-09-04 5:00 ` Gabe McArthur [this message]
2009-09-04 7:33 ` Mark Struberg
2009-09-04 12:22 ` Jonas Fonseca
2009-09-04 12:27 ` Mark Struberg
2009-09-04 12:41 ` Jonas Fonseca
2009-09-04 12:47 ` Mark Struberg
2009-09-03 1:23 ` Shawn O. Pearce
2009-09-03 19:46 ` Nasser Grainawi
2009-09-03 19:49 ` Shawn O. Pearce
2009-09-03 21:09 ` Nasser Grainawi
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 7:12 Mark Struberg
[not found] <ed88cb980909040744k2fa372fapb7ee457c745b9aa0@mail.gmail.com>
2009-09-04 14:49 ` Mark Struberg
2009-09-04 17:28 ` Mark Struberg
2009-09-04 18:50 ` Jonas Fonseca
2009-09-04 18:54 ` Mark Struberg
2009-09-04 19:51 ` Mark Struberg
2009-09-04 23:47 ` Gabe
2009-09-05 0:06 ` Douglas Campos
2009-09-05 1:29 ` Gabe McArthur
2009-09-05 16:25 ` Robin Rosenberg
2009-09-05 16:40 ` Mark Struberg
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=loom.20090904T064602-511@post.gmane.org \
--to=gabriel.mcarthur@gmail.com \
--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.