|(no subject) [message #721091 is a reply to message #720982]
||Wed, 31 August 2011 20:12
| Robin Rosenberg
Registered: July 2009
Randall Becker skrev 2011-08-31 17.58:|
> We've currently got a substantial investment in ClearCase automation,
> implemented through their CM API and plugged in to our own ECLIPSE
> plug-in. Looking at EGit, we're trying to work out the effort involved
> in moving the underlying SCM provider to EGit, but haven't found any way
> to migrate our automation layer. Is there some form of API available
> (classes, messages, procedures, etc.) for driving capabilities in EGit,
> including version inquiries?
At the Git level everything is implemented by JGit. EGit is the layer
that binds JGit to Eclipse.
Try to stick with the org.eclipse.jgit.api package as the primary
entry point into JGit.
At the level of integration with Eclipse there is no "API", everything
is internal, except where we hook into Eclipse for the Team operations.
The Team API is very file oriented and does not reveal the capabilities
of Eclipse very well, so you probably want to use JGit for the Git
operations, but use the Ecliose API:s to get handles to your project.
Clearcase and Git are so different that switching SCM might be an
Powered by FUDForum
. Page generated in 0.01560 seconds