git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: jgit as a jira plugin

From
Shawn O. Pearce <spearce@spearce.org>
Date
Oct 29, 2008, 23:08 UTC
Message-ID
<20081029230816.GA31926@spearce.org>
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.
Previous: J. LongmanNext: J. Longman
Message 2 of 5 in “jgit as a jira plugin”
  1. J. LongmanOct 29, 2008
  2. Shawn O. PearceOct 29, 2008
  3. J. LongmanOct 29, 2008
  4. Shawn O. PearceOct 29, 2008
  5. Shawn O. PearceOct 31, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.