git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jonas Fonseca" <jonas.fonseca@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Farrukh Najmi" <farrukh@wellfleetsoftware.com>, git@vger.kernel.org
Subject: Re: Newbie questions regarding jgit
Date: Tue, 11 Nov 2008 23:01:01 +0100	[thread overview]
Message-ID: <2c6b72b30811111401i3c995889n54407243a1072599@mail.gmail.com> (raw)
In-Reply-To: <20081111214434.GS2932@spearce.org>

On Tue, Nov 11, 2008 at 22:44, Shawn O. Pearce <spearce@spearce.org> wrote:
> Jonas Fonseca <jonas.fonseca@gmail.com> wrote:
>> I would also like to have a public available maven repository for
>> JGit. If Shawn or Robin acks, I can look into hosting one in the SVN
>> area of the Google Code project page. Given the lack of a real release
>> cycle it probably only makes sense to have a snapshot repository.
>
> I have an account on kernel.org and was planning on hosting snapshots
> there, but I haven't had time to think about setting up a jgit area
> and pushing something into it.  ;-)

If you prefer that ...

> We could also just host it in SVN in Google Code.  I can give
> you admin rights on the egit project if you want to set it up and
> maintain it there.  The downside is you need to use svn or git-svn
> to upload files to it, right?

I don't think admin rights are necessary as long as I have
"commit"/webdav access. And no svn or git-svn interaction should be
needed to upload to the maven repository.

Take a look at the distributionManagement section of the
google-maven-repository:

 - http://google-maven-repository.googlecode.com/svn/repository/com/google/google/1/google-1.pom

Looks pretty easy to set up. About maintaining it, I don't mind doing
"mvn deploy" once in a while, but some kind of update policy should
probably be worked out in any case.

-- 
Jonas Fonseca

  reply	other threads:[~2008-11-11 22:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 20:44 Newbie questions regarding jgit Farrukh Najmi
2008-11-11 21:12 ` Farrukh Najmi
2008-11-11 21:37 ` Jonas Fonseca
2008-11-11 21:44   ` Shawn O. Pearce
2008-11-11 22:01     ` Jonas Fonseca [this message]
2008-11-11 23:11       ` Shawn O. Pearce
2008-11-11 23:48         ` [PATCH] Add maven distribution management info for the new snapshot repository Jonas Fonseca
2008-11-12  0:58           ` Shawn O. Pearce
2008-11-12  1:01             ` Shawn O. Pearce
2008-11-12  2:24         ` Newbie questions regarding jgit Imran M Yousuf
2008-11-12 12:51       ` Farrukh Najmi
2008-11-12 14:05   ` Farrukh Najmi
2008-11-12 14:33     ` Farrukh Najmi
2008-11-12 17:56       ` Farrukh Najmi
2008-11-12 18:30         ` Jonas Fonseca
2008-11-12 19:29         ` Shawn O. Pearce
  -- strict thread matches above, loose matches on Subject: below --
2008-11-12 22:36 Robin Rosenberg
2008-11-12 22:37 Robin Rosenberg

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=2c6b72b30811111401i3c995889n54407243a1072599@mail.gmail.com \
    --to=jonas.fonseca@gmail.com \
    --cc=farrukh@wellfleetsoftware.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.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 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).