Re: [JGIT RFC] Mavenized JGit

From: Shawn O. Pearce <spearce@spearce.org>
Date: Jun 4, 2008, 04:27 UTC
Message-ID: <20080604042703.GQ12896@spearce.org>
In-Reply-To: <7bfdc29a0806032052w39010711q27e5257ef559908a@mail.gmail.com>

Imran M Yousuf <imyousuf@gmail.com> wrote:

> The first version I mavenized JGit I moved the source code, but I
> thought that would come in for more criticism :), thus I chose the
> symlink option. Please let me know if a move based mavenizing would be
> welcomed or not.

[please don't top-post on this list]

I'd rather us moving the code into a subdirectory than require a symlink. For Eclipse this is easy to change the directory that the code is in, we just have to edit the .classpath to move the source folder lower in the tree.

But this shows one reason why I don't use Maven I think. The fact that we need a "java" directory to hold our java code. What if another build system wants a different name? Grumble.

For the most part git-merge-recursive can handle a merge through
this sort of rename.  But we'd like to do this sort of thing at
some relatively stable point in time to try and minimize the impact
it has.

Show 7 quoted lines

> On Wed, Jun 4, 2008 at 5:30 AM, Robin Rosenberg
> <robin.rosenberg.lists@dewire.com> wrote:
> > onsdagen den 4 juni 2008 00.54.18 skrev Shawn O. Pearce:
> >> I don't think there is a Cygwin based version of the JVM.  That would
> >> be a very interesting beast.
> > Looks like it could be possible to build it under Cygwin.
> > http://download.java.net/jdk7/docs/build/README-builds.html#cygwin

-- 
Shawn.