java - Confusion in choosing between JavaGit, JGit and EGit -


I am creating a Java application that uses GIT I found that there is something called, and

I know that the javascript and the ejeet / jagitt are different I do not understand what is the difference between ejeet and jajit. Both are hosted on Elypes projects, but one feels related to eclipse and not another.

I do not use Eclipse and I do not plan for it, so I do not really care about "eclipse integration"

Is jezet connected to eclipse somehow is? (This is hosted at www.eclipse.org, and JGIT has many "eclipse" keywords)

For all three, I would need to add my Java program (not written Eclipse To work with GIT repository?

I would prefer a standalone GIT library (i.e., on the basis of local GIT installations)

Edit: Another question:

  • What jazz support?

    Edit: I got the answer - It does so (have not tried to do this yet) in this transport package bundle vter

    )

    You can use JGIT as a standalone library but, as That is mentioned in:

    can be found within JGIT:
    * EGIPS, Eclipse Team Provider for GIT

    In that sense, Zegit ekl Linked to ips, which EGiment has used JGT features to develop the Eclipse Git plugin.
    Keeping in view of all eclipse projects, now the GIT repo has been made (instead of earlier CVS repo), I will consider the widget for your java project, as it seems that:

    • The Javascript has not been updated for some time (2008)
    • Eclipse is committed to providing a good support for GIT through EGIT, which will ensure the development of JGIT in detail in detail Should (EGIT Is used).

      Comments:

      Whether Aggt uses JGT, it is not quite clear in later versions that EGIT is an Eclipse plugin For which GIT has supported GT, I have a way that CVS is already supported in Eclipse

      Emigration of eclipse projects, and (by Chris Aniszkaz)

      I have several projects from the CVS to Git project in DevList Monitoring of the conversation about the code of the code.
      Most developers, it seems, understand the value proposition to migrate, despite their worries that there is a lot of new learning with migration ???? As they understand how to say the producers in a new environment.

      Essentially, the discussion about the team provider for the guit developed by the EIGT project becomes a major part of the conversation. Is AGIT ready for primetime?

      The official bug has shown an Eclipse commitment to provide "adequate tooling support" for all eclipse projects now on Git Repo.

      To reduce the old VCS in favor of GIT, sufficient tooling should be available. This bug is designed to be tracked.
      [...] I have opened / linked relevant EGit worms for a better visibility / tracking of what has been lost.

      Then Agit is the only project referred to in that bug, which provides adequate tooling support for the new (D) VCS chosen for all Eclipse projects.

      ( Old VCS tool , which essentially includes CVS.)

      Bus (March 17, 2001): < / Strong> ():

      Iâ € ™ m glad that since last year, things have been coming very long, based on community contribution to eclipse market statistics and projects.

      EGIT installation rate

      So what's next? In terms of tooling, we are getting close to our 1.0 release (which has been planned for the Indigo release).
      GIT tooling on eclipses is much better these days, if you need help or have any questions, please start with the best .

      If you are for a eclipse.org project, please consider starting the process to transfer your project repository to the .
      It would be good to see that the plans of going to the Guit by the Indigo release of Eclipse.org projects.

Comments

Post a Comment