VersionVault views and Eclipse workspaces

When using the HCL VersionVault Explorer for Eclipse, use a separate Eclipse workspace for each VersionVault view that you create.

Because the contents of a VersionVault view are determined by its configuration specification (and for some view types, by load rules), only one version of a resource is valid in any VersionVault view at a time. A VersionVault view selects a consistent set of versions. If you import projects from multiple VersionVault views into a single Eclipse workspace, the workspace may reference an inconsistent, incompatible combination of resources.

There are two ways to create an Eclipse workspace to associate with a VersionVault view:

  • You can create the VersionVault view, then use the Eclipse File > Switch Workspace->Other command to create a new workspace and switch to it.
  • You can create the workspace first, by starting Eclipse with the command line argument -data workspace-path, where workspace-path is the path to the workspace that you want to associate with a VersionVault view that you plan to create.

Regardless of the way in which you choose to create the Eclipse workspace, consider creating the workspace in a folder whose name is based on the VersionVault view tag of the view with which the workspace is associated.