| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML> |
| <HEAD> |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> |
| <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| |
| <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> |
| <TITLE>Repository providers</TITLE> |
| |
| <link rel="stylesheet" type="text/css" HREF="../book.css"> |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <H2> |
| Repository providers</H2> |
| <P > |
| A repository provider (<b><a href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>) is the central class in the implementation of your |
| repository. This class is responsible for configuring a project for |
| repository management and providing the necessary hooks for resource |
| modification. Providers are mapped to a project using <a href="resInt_properties.htm">project |
| persistent properties</a>. The mechanism for mapping providers to a |
| project is not central to the team API, but you'll need to be aware of it when |
| filtering out resources in your UI. For the most part, you'll be using |
| team API to work with projects and associate them to your provider. </P> |
| <P > |
| To implement a provider, you must define a repository using <a href="../reference/extension-points/org_eclipse_team_core_repository.html"><b>org.eclipse.team.core.repository</b></a> |
| and supply a class |
| derived from <b><a href="../reference/api/org/eclipse/team/core/RepositoryProvider.html">RepositoryProvider</a></b>. We'll use the CVS client as an example to see how this |
| works.</P> |
| |
| <p> |
| |
| </p> |
| |
| |
| |
| |
| <p><a href="../hglegal.htm"><img border="0" src="../ngibmcpy.gif" alt="Copyright IBM Corporation and others 2000, 2003." border="0" width="324" height="14"></a></p> |
| </BODY> |
| </HTML> |
