git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Farrukh Najmi <farrukh@wellfleetsoftware.com>
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>, git@vger.kernel.org
Subject: Re: ETA for release of gjit 0.4?
Date: Mon, 8 Dec 2008 08:21:23 -0800	[thread overview]
Message-ID: <20081208162123.GD31551@spearce.org> (raw)
In-Reply-To: <493ACAFC.5040605@wellfleetsoftware.com>

Farrukh Najmi <farrukh@wellfleetsoftware.com> wrote:
>
> I could but maven (and good project release) practices are that a  
> project's release version should be managed by the project and not  
> consumers of the project.
>
> BTW, If there is interest in maveninzing the project I can offer to  
> contribute that change to the project. Just let me know if that is  
> something the project wishes to do.

Have you seen the jgit-maven subdirectory?  It has a jgit/pom.xml
contributed by Imran M Yousuf for exactly this reason.  I think we
also have a Maven distribution site:

  http://code.google.com/p/egit/wiki/ConfiguringMaven

The issue is getting one of the developers to tag and upload a build.
Myself, I don't actually use Maven, so I don't build with it.

-- 
Shawn.

  reply	other threads:[~2008-12-08 16:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 14:34 ETA for release of gjit 0.4? Farrukh Najmi
2008-12-06 18:47 ` Robin Rosenberg
2008-12-06 18:57   ` Farrukh Najmi
2008-12-08 16:21     ` Shawn O. Pearce [this message]
2008-12-08 16:35       ` Farrukh Najmi
2008-12-15 22:52         ` Farrukh Najmi
2008-12-16  3:56           ` Robin Rosenberg
2008-12-16  4:17           ` Robin Rosenberg
2008-12-16  4:23             ` Robin Rosenberg
2009-01-14  3:14             ` Jonas Fonseca
2008-12-08 16:52   ` Shawn O. Pearce
2008-12-08 17:13     ` Shawn O. 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=20081208162123.GD31551@spearce.org \
    --to=spearce@spearce.org \
    --cc=farrukh@wellfleetsoftware.com \
    --cc=git@vger.kernel.org \
    --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).