From: "Shawn O. Pearce" <spearce@spearce.org>
To: "J. Longman" <longman@xiplink.com>
Cc: git@vger.kernel.org
Subject: Re: jgit as a jira plugin
Date: Wed, 29 Oct 2008 16:08:16 -0700 [thread overview]
Message-ID: <20081029230816.GA31926@spearce.org> (raw)
In-Reply-To: <5915DAE3-7BDF-4296-9DB3-6FBEE504A317@xiplink.com>
"J. Longman" <longman@xiplink.com> wrote:
> I've integrated jgit into a plugin for the Jira Issue tracking system.
> There is more information here:
> http://confluence.atlassian.com/display/JIRAEXT/Jira+Git+Plugin
Cool!
> 1) I noticed that there is a maven pom file. Are you present in a maven
> repository? Also any problem with embedding a working snapshot in my
> plugin?
No, we aren't hosted in any repository yet. The pom file exists to
make it easier for people who prefer maven to build, but its not the
primary build system for jgit.
> 2) I'd like to find out the jgit way to achieve the equivalent of 'svn
> update'. I understand that fetch can do this but being new to git, I
> don't really understand quite what I need yet. The goal is to have git
> the latest commits from the origin before indexing.
Use a Transport instance to execute a default fetch (no args) on say
the "remote" origin. That will download the objects to the local
database, but it won't update a working directory. But I'm not sure
you would care about the working directory in the backend of Jira.
> Thanks for jgit - it took me a day or two to wrap my head around getting
> the list of files changed in a commit but otherwise its great to have
> something that can be integrated into jira.
Yea, about that, we wanted to write more tutorials on the API... ;-)
--
Shawn.
next prev parent reply other threads:[~2008-10-29 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 23:02 jgit as a jira plugin J. Longman
2008-10-29 23:08 ` Shawn O. Pearce [this message]
2008-10-29 23:49 ` J. Longman
2008-10-29 23:53 ` Shawn O. Pearce
[not found] ` <C9B1B0D7-6F99-48DE-8593-A13F1187ADE2@xiplink.com>
2008-10-31 14:42 ` 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=20081029230816.GA31926@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=longman@xiplink.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).