Set Vault Association

This topic describes the Set Vault Association dialog box, which appears when Set Vault Association is selected. It is used to change the vault association or selector for a project.

If you need to change the vault association of your project, for example, if you move the product to a different server, you can use the Set Vault Association dialog to create the connection between the local workspace and the source control server.

You cannot set the vault association on a module folder.

Note: Eclipse projects must be in a single module.

This page discusses:

Set vault association optionsModify the vaultModify the SelectorApply changes recursivelyCommand InvocationCommand Buttons

Modify the vault

The vault path to the project on the DesignSync server.

By default, the checkbox is selected and the vault prefilled with the vault folder path, or if no path has been selected, the current working folder path.

Modify the Selector

The design objects version designator. You can specify:

  • A branch selector, typically Trunk:.
  • A project configuration, as created using ProjectSync, that has been applied to the project vault you are accessing.
  • A version selector, typically Latest, which always resolves to the latest version on a specific branch.

By default, the checkbox is selected and the selector prefilled with the current selector, or if no path has been selected, Trunk.

Apply changes recursively

When checked, recursively clears any vault information that may have been set in subfolders. When you are setting the vault for the first time, checking this option has no effect.

When not checked, any previously set vault information in subfolders remains.

When you set the vault on a folder, that vault association is stored in the local metadata for that folder. Each subfolder inherits its vault association from its parent folder; the vault association is not stored in metadata unless the subfolder has an explicit set vault association applied to it.

Every versionable object (file or collection) in the hierarchy inherits its vault from the parent folder, although once a revision-control operation has been performed on the object, the vault association is stored in that object's metadata. Therefore, anytime you want to change a vault setting (as opposed to setting the vault for the first time), check the apply change recursively option. This removes all vault associations that are stored in metadata, which causes all objects in the hierarchy to inherit their vault associations from the folder on which the set vault association has been applied.

Note: The recursive option is not valid for modules and is ignored.
Important: If a subfolder had an explicit set vault association applied to it such that the vault information is stored in the folder's local metadata, that vault association is removed and the subfolder reverts to inheriting its vault association from the parent folder.

Other

These sections appear on most dialog boxes

Command invocation
See Command Invocation.
Command buttons
See Command Buttons.