.
A project set holds specific information needed to reconstruct a set of projects from a team repository to the workspace. Only projects that are shared can be part of a project set.
For example, project sets can be used to group projects for a release or for contributing it to another person.
Project sets are stored in xml files with the file extension psf.
In the eclipse views the files are displayed with the icon
.
The format of the project set file used by this plugin is the same that is used in eclipse when exporting or importing team project sets.
In the Project Set Editor for each project it can be specified to which local directory it will be stored for the first time it is loaded. If no such preferred location is specified it will be stored to the eclipse workspace directory. If the project is already stored to an other location, this location will be used when loading the project.
The information about the preferred project locations is stored in an additional
file which has the same name as the project set file but with the file extension .ppl.
The .ppl file will be shown with the icon 
and will be created the first time the user specifies a preferred project location
in the project set editor and then saves the project set.
Placeholders for path segments can be used in the preferred project locations. The syntax to be used is ${Variablename}, for example "${myroot}/subfolder" can be set as preferred location and every user can define his own root directory. Every variable must be defined in the preference page for the project sets. The pathvariable ${workspace} is always defined implicitly with the path to the eclipse workspace directory. Project sets with undefined variables can not be loaded.
The specified preferred local directory will be deleted before loading the project from the team repository. Please specify always the complete path of the directory to which the project files should be loaded. For example if you set C:\ as preferred local directory the hard disk will be completely deleted !
When loading a project with a preferred local directory always the message dialog "The project already exists. Do you wish to overwrite ist ?", even if the project not exists before. For technical reasons this message can currently not be supressed. Please confirm it with "Yes".
To create a project set file use the menu "File > New > Other...", select the category "Project Set" and the type "Project Set".
The Wizard for creating a new project set has two pages.
On the first page you can specify the name of the project set file and the destination folder.
On the second page you select the projects that will be in the project set. Only shared projects that are loaded in the workspace can be added. They will be added in the tag that is loaded in the workspace. This dialog has some buttons to simplify the selection (e.g. select all projects of a working set). If the checkbox "Select referenced" is on then all referenced project will be recursively selected. The referenced projects will not be deselected automatically if a project if deselected.
Note: To create a project set file you can also use the menu "File > Export..." and select "Team Project Set"
To edit a project set file
An Editor for the project set will then be opened. How to use this editor is described in Project Set Editor
The projects referenced in a project set file can be added to the workspace by
If a project is already loaded in the workspace you will be asked if the content should be overwritten.
Repository locations in project sets distinguish between server names and IP addresses. This means if one user has the repository specified by the server name and and an other user uses the IP address of the server (or an other name for the same server) this will cause problems, e.g. the projects will be shown to one user as "loaded in an other version" although the same version of the physically same server is loaded. It is recommended to use the server name instead of the IP address.
To avoid problems when changing the server location of a repository we recommend to use different symbolic server names for each repository. Each user must map the symbolic names in the hosts file to the real server names or IP addresses. On Windows NT/2000 the hosts file is located C:\WINNT\system32\drivers\etc.