Re: [EGIT PATCH 00/31] Push GUI, GUI improvements, various jgit stuff

["Shawn O. Pearce" <spearce@spearce.org>]

Marek Zawirski <marek.zawirski@gmail.com> wrote:
> Shawn O. Pearce wrote:
>>
>> I've thought about starting a code.google.com project just to use
>> the issue tracking system there.
>
> That seems to be nice idea.
> The only downside I see is that using code.coogle.com with Mylyn may be  
> hard[1]. As if we start to use issues system, it may be nice opportunity  
> to start using Mylyn - if anybody want to?
>
> [1] http://www.jroller.com/alexRuiz/entry/using_mylyn_with_google_code

A comment there suggests its gotten slightly better:

Posted by Christopher Barber on July 17, 2008 at 02:26 PM PDT:
> There was a regression introduced in the 3.0 version of mylyn,
> but it has been fixed in 3.0.1, which was just released.
> 
> Also, since Google Code now supports csv output, you are probably
> better off changing your Query URL to:
> 
> ${serverUrl}/csv?can=1&colspec=ID+Status+Type+Owner+Summary
> 
> and your Query Pattern to:
> 
> "({Id}[0-9]+?)","({Status}.+?)","({Type}.+?)","({Owner}.+?)","({Description}.+?)"\n
> 
> This should provide a faster sync, since it minimizes the amount
> of bytes downloaded.

I may give it a try later today.

I also know some of the folks behind code.google.com.  I can poke
them to see if Mylyn support is going to be coming along in the
near future.  Google uses Eclipse a lot internally, and we have
a number of open source projects using code.google.com as their
hosting/issue tracking, and Eclipse as their IDE.  We probably
should be making the issue tracking product more accessible to IDEs.

-- 
Shawn.