Using Eclipse team project sets with VersionVault

When you use the Eclipse export wizard to create Team Project Set, you can place it in an HCL VersionVault repository to make it easy for team members to import the project set. Importing a Team Project Set file loads all of the resources in the project set into a VersionVault view and imports them into the associated Eclipse workspace.

Working with project set files that have been added to source control

When you use the HCL VersionVault Explorer for Eclipse, you can take advantage of the integration between VersionVault and Eclipse Team services to simplify the process of loading project resources from a VOB into a VersionVault view and importing those resources into the associated Eclipse workspace.

When you import an Eclipse Project Set from a project set (*.psf) file that has been added to source control:

  1. Resources from all projects in the set are loaded into the VersionVault view from which you selected the project set file.
  2. All projects in the set are imported into the Eclipse workspace associated with the view.
Note: Project resources are loaded even if they have been moved or renamed since the project set file was created, as long as they have not been moved to a different VOB.

Working with project set files that are not under source control

When team members use project set files that are not under VersionVault source control (for example, project set files that have been distributed by e-mail or copied from another computer), they must place the project set file in the copy area of a VersionVault view before importing the project set. (The project set file does not need to be added to source control and can be placed anywhere in the view's copy area.)