From: Jonas Fonseca <fonseca@diku.dk>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Farrukh Najmi <farrukh@wellfleetsoftware.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: ETA for release of gjit 0.4?
Date: Wed, 14 Jan 2009 04:14:35 +0100 [thread overview]
Message-ID: <20090114031435.GA31274@diku.dk> (raw)
In-Reply-To: <200812160517.33975.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote Tue, Dec 16, 2008:
> Jonas, could you help us on this:
Sorry for the long delay. I completely overlooked this. In case it is
still relevant ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Error deploying artifact: Failed to transfer file: http://egit.googlecode.com/svn/maven/snapshot-repository//org/spearce/jgit/0.4.0/jgit-0.4.0.jar. Return code is: 401
>
> I added this (nah, naming it release-repository didn't work either)
>
> <repository>
> <id>jgit-maven-release-repository</id>
> <name>JGit Maven Release Repository</name>
> <url>https://egit.googlecode.com/svn/maven/snapshot-repository/</url>
> <uniqueVersion>true</uniqueVersion>
> </repository>
This will end up mixing snapshots and releases ...
> (tried all combinations of dav/not-dav, http/https). Seems I don't have a dav provider,
> but https should work, right?
Well, I don't know, but I would expect the "dav:" to be required. I used
the Google Maven Repository pom.xml[0] as a template, which should give
something like:
<repository>
<id>jgit-maven-repository</id>
<name>JGit Maven Repository</name>
<url>dav:https://egit.googlecode.com/svn/maven/repository/</url>
</repository>
[0] http://google-maven-repository.googlecode.com/svn/snapshot-repository/com/google/google/1-SNAPSHOT/google-1-20080826.150842-5.pom
> and to ~/.m2/settings.xml
>
> <servers>
> <server>
> <id>jgit-maven-snapshot-repository</id>
> <username>tried both my project email and gmail email</username>
> <password>nah, won't show you</password>
> </server>
> </servers>
Try:
<servers>
<server>
<id>jgit-maven-repository</id>
<username>robin.rosenberg</username>
<password>Password from http://code.google.com/hosting/settings</password>
</server>
</servers>
Hope this helps.
--
Jonas Fonseca
next prev parent reply other threads:[~2009-01-14 3:16 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
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 [this message]
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=20090114031435.GA31274@diku.dk \
--to=fonseca@diku.dk \
--cc=farrukh@wellfleetsoftware.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
--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).