Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Mail Systems
Eclipse Documentation

How To Guides
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Problem Solutions
Privacy Policy




Eclipse Plug-in Developer Guide
Previous Page Home Next Page

Team Repository Provider



The Team plugin contains the notion of Repositories. The job of a repository is to provide support for sharing resources between Team members. Repositories are configured on a per-project basis. Only one repository can be mapped to a project at a time.

Repositories that extend this extension point can provide implementations for common repository specific rules for resource modifications, moving and deleting. See the following interfaces for more details IFileModificationValidator and MoveDeleteHook.

A Repository type can also be specified in order to provide non-project specific funtionality such as a

Optionally, a repository provider type can designate that it can import projects from a second provider, in the case where the second provider's plugin is not available in the current install. This is provided as a means to support the migration from one provider implementation to another where the resuse of the same id for the two providers was not possible.

A repository provider type can also specify one or more meta-file paths (delimited by comas) that are relative to a parent container. If an unshared project or folder contains files that match all the meta-file paths associated with a repository definition, the method RepositoryProviderType#metaFilesDetected will be invoked with the parent container as an argument. This is done to give the repository type a chance to mark the files team-private and potentially share the project as well. see the javadoc of the above mentioned method for more details.

Configuration Markup:

<!ELEMENT extension ( repository)>

<!ATTLIST extension



<!ELEMENT repository EMPTY>

<!ATTLIST repository

id               CDATA #IMPLIED

class            CDATA #REQUIRED

typeClass        CDATA #IMPLIED

canImportId      IDREF #IMPLIED

metaFilePaths    CDATA #IMPLIED

fileSystemScheme IDREF #IMPLIED


  • id - an optional identifier of the extension instance
  • class - the fully-qualified name of a subclass of
  • typeClass - the fully-qualified name of a subclass of
  • canImportId - ID of another team provider this provider can import from
  • metaFilePaths - Comma separated list of file paths that are considered to be version control metadata. If any of these files are detected in a newly imported project the provider's Repository Provider Type will be notified so the project can be mapped to the provider.
  • fileSystemScheme - This field identifies the scheme of a filesystem registered with the org.eclipse.core.filesystem.filesystems extension point


<extension point=





Supplied Implementation:
The provided implementation of RepositoryProvider provides helper methods and common code for mapping and unmapping providers to projects. The optional RepositoryProviderType provides project set import and export through a ProjectSetCapability.

Copyright (c) 2005, 2008 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at

  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire