We used to do this all the time with SourceOffsite but Vault apparently does not allow this: Two distinct projects pointing to the same working folder.
Here's why we need this:
"Project A" contains usual files for source control.
"Project A (no clobber)" contains files for development that are WORKSTATION SPECIFIC or DATA and FILES WE DON'T WANT ARBITRARILY REFRESHED. Things like configuration files and data files that are workstation, network, or context-specific. Typically the developer would download these once and that's it.
We will also need to map various versions of test data to the same physical disk folder.
Question: how can we map two different vault folder trees to the same physical disk tree? This was possible in both SourceOffsite and VSS and it's great.
Two projects, same working folder
Moderator: SourceGear
-
StevenBlack
- Posts: 13
- Joined: Sat Apr 05, 2008 7:20 pm
- Location: Canada
Steven,
This is a feature that Vault doesn't (and probably will not ever) have. The number of issues that arise when working folders are mapped in this manner make it very difficult for Vault to handle this case.
A workaround for you, though since you know that you don't want to check one set of files in, is to do a Get To Non Working Folder for that set. The way you would do this in the GUI client is to fill in the path in the text box at the top of the Get dialog.
This is a feature that Vault doesn't (and probably will not ever) have. The number of issues that arise when working folders are mapped in this manner make it very difficult for Vault to handle this case.
A workaround for you, though since you know that you don't want to check one set of files in, is to do a Get To Non Working Folder for that set. The way you would do this in the GUI client is to fill in the path in the text box at the top of the Get dialog.