Command Line GET With Working Folders

[davecourt]

Hi

I am using the following file structure within my vault server:

Project Name
Branches
Version 1
Version 2
Trunk
(Live Code)

When I run the get command from the command line I want the folders to use the working folders I have set for them because I don't want the file structure above to appear on my system but just the files within the trunk directory. I have therefore set the top level folder ($) to have a working directory of a given location and then set individual working folders for each trunk directory.

When I run get from the command line without a -destpath flag, it gets upset that I have not specified a path. In the commandline help however it does state that -destpath will be used if no working folders have been set. I thought by setting the root folder working directory, it would be recursive through the sub folders unless I changed an individual sub folder?? At the moment I have to put a -destpath in which pulls everything to the wrong place.

I hope this makes some sense to someone.

Thanks

Dave

[jclausius]

When I run get from the command line without a -destpath flag, it gets upset that I have not specified a path.

What does this mean? What is the error message?

In the Vault 2.0.x command line client (CLC), if -destpath is not specified, the client will try to use the working folders assigned for that user.

A quick suggestion - Have you viewed the working folders in the CLC for the repository (-LISTWORKINGFOLDERS). Use the same repository / user /password as your get command. Does this list match your expectations? If not, modify the working folders in the CLC or Vault GUI.

[davecourt]

Thanks for that - interesting because setting the working folder in the GUI didn't seem to have any affect at all?

Setting the working folder on the command line seemed to solve the problem though.

Very strange?

Thanks

[jclausius]

A couple of things could be affecting this.

1) Using the CLC while logged in as a different Windows than when you used the Vault GUI.

2) Using a different user in the Vault CLC than the Vault GUI.