Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
FAQ What is the difference between a repository provider and a team subscriber?
The Eclipse Platform team component supports two
categories of tool integration. Of primary interest are repository providers,
which represent full-fledged versioning and configuration management tools,
such as CVS, ClearCase, and Subversion.
These tools typically include support for maintaining an arbitrary number of
versions of files and file trees, for branching and merging development
streams, and for linking versions to bug tracking and other configuration
management tools. Clients for interacting with these tools are represented
in Eclipse through the RepositoryProvider API.
Another class of team tooling is used for deployment of development
artifacts to a remote execution target. For example, you may use
FTP or WebDAV to deploy code and other resources to a Web server,
or a proprietary protocol for deploying code to embedded and hand-held
devices. This class of tooling is represented by the team subscriber API.
Note the extensive overlap between these two categories of team tooling. In general, team subscribers represent a subset of the functionality provided by a repository client. In other words, if you’re writing a client for a repository, you will most likely need both the repository provider and the team subscriber API.
See Also:
FAQ_What_APIs_exist_for_integrating_repository_clients_into_Eclipse?
FAQ_How_do_I_deploy_projects_to_a_server_and_keep_the_two_synchronized?
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.