|
| Re: Team API Usage Question [message #198825 is a reply to message #198783] |
Fri, 20 February 2004 21:16  |
Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
Paul,
The Team plugin (org.eclipse.team.core) is dependant on the resources
plugin (org.eclipse.core.resources) so any RCP app that used team would
need to be IResource based at least for the resources under version
control. Including the UI portion has further dependencies (i.e. you'd
end up with most of the platform SDK plugins).
Also, there is no Team API that allows third party tools to invoke
repository funtionality. The API is really there to provide integration
points for repository providers. If you plan on using a particular
repository type (e.g. CVS) you may want to investigate developing a
small client that does only what you need.
If you want to discuss this further, the platform-team-dev mailing list
may be a better place.
Michael
Paul Wuethrich wrote:
> The requirements are to provide team-like functionality to an RCP
> application for version control over a small set of domain specific files.
> The end-users will be "business" users and so a full blown CVS
> implementation is not required.
>
> The current plan is to extend the Team api. Is there any reason NOT to use
> the Team plugins and build the versioning functionality from the ground up?
> I'm guessing not but I have limited experience in this area and have used
> the CVS client and experimented with the file system example.
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03679 seconds
] 
Search
Help
Register
Login
Home
