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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html