git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Imran M Yousuf <imyousuf@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [JGIT RFC] Mavenized JGit
Date: Tue, 3 Jun 2008 18:54:18 -0400	[thread overview]
Message-ID: <20080603225418.GP12896@spearce.org> (raw)
In-Reply-To: <200806031856.11060.robin.rosenberg.lists@dewire.com>

Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> tisdagen den 3 juni 2008 16.42.33 skrev Imran M Yousuf:
> > I have successfully Mavenized JGit (at least partially :)) to make it
> > independent of IDE to develop on. I will also add a code-file format
> > checker soon. Please have a look at it and let me know what you think
> > and how it can be improved. If its helpful I will surely send out a
> > patch in this regard. The one thing that I did not configure is the
> > external test (exttst), doing that and the code format checker is my
> > next step.
> > The 'jgit-mavenize' branch of my fork of egit contains it.
> > (http://repo.or.cz/w/egit/imyousuf.git?a=shortlog;h=refs/heads/jgit-mavenize).
> 
> An abvious problem is that JGit does not handle symbolic links and those do
> not work well (if at all) under git on windows either. Cygwin will not do here,
> unless you accompany it with a cygwin java build (if such a thing exists). Mingw
> also does not support them.

I'm all for a change that widens the group of applications and
users that can use jgit (heck, that's one reason we moved to it to
a BSD license).  But we really cannot abandon Windows users in that
process, so yea, anything that tries to use symlinks is bad.

I don't think there is a Cygwin based version of the JVM.  That would
be a very interesting beast.

-- 
Shawn.

  reply	other threads:[~2008-06-03 22:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 14:42 [JGIT RFC] Mavenized JGit Imran M Yousuf
2008-06-03 16:56 ` Robin Rosenberg
2008-06-03 22:54   ` Shawn O. Pearce [this message]
2008-06-03 23:30     ` Robin Rosenberg
2008-06-04  3:52       ` Imran M Yousuf
2008-06-04  4:27         ` Shawn O. Pearce
2008-06-04  6:40           ` Nigel Magnay
2008-06-04  6:46             ` Imran M Yousuf
2008-06-04 19:59               ` Shawn O. Pearce
2008-06-05  2:31                 ` Imran M Yousuf
2008-06-06  5:28                 ` Imran M Yousuf
2008-06-06 11:59                   ` Robin Rosenberg
2008-06-06 12:40                     ` Imran M Yousuf
2008-06-04  6:45           ` Imran M Yousuf
2008-06-05  3:23             ` Ittay Dror
2008-06-05  3:33               ` Imran M Yousuf
2008-06-06  5:31               ` Imran M Yousuf

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=20080603225418.GP12896@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=imyousuf@gmail.com \
    --cc=robin.rosenberg.lists@dewire.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).