The current state of the module is basically a prototype, which I created over the course of a few weeks. Unfortunately, I have had only little time to spend on it after it got merged due to 99% of my usage got covered.
Personally, I am not opposed to switching back to CGit or offering both with JGit as a fall-back, if you think it will help create a great git module faster and get more people involved (including you). However, I think it would be wrong to completely abandon JGit, since it offers some nice features, which will allow a "native" gitk-like TopComponent that I think is an improvement over the current history browser. On Wed, Apr 29, 2009 at 14:05, Lincoln Stoll <[email protected]> wrote: > Is JGit still definitely the way forward? I've forked off the old cli > branch, and made a few hacks to get status (including ignored) and > committing working properly, and I'm probably going to do further work > here. I'm dogfooding it myself, and much happier now ignored files > aren't showing up in the list. It still needs plenty of other features > added, but correct status and committing is 99% of my usage. > > It's not just the .gitignore thing, but JGit also doesn't seem to > support submodules, instead throwing an exception - which is > frustrating. I note that one of the reasons for choosing JGit was > better cross platform, and tighter integration. Command line seems > good enough for the mercurial module and the IntelliJ git module, plus > git is getting much better on windows. > > Thoughts? -- Jonas Fonseca --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nbgit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nbgit?hl=en -~----------~----~----~----~------~----~------~--~---
