commit by means of cmd client fails
Moderator: SourceGear
commit by means of cmd client fails
Hi there,
I have two set of checked out files, first set is checked out to "c:\s\u" and other one to "e:\1\2\3" and I want to check in only first set of files.
To do that I am using cmd client with next cmd line:
"D:\Program Files\SourceGear\Vault Client\vault.exe" -user User - password "Password" -host Host -repository "Name" commit "$/s/u" -unchanged checkin
It returns me an error:
<vault>
<error>
$/s/u does not exist in the current change set.
...
But gui client shows that pending change set contains that files.
Where am I wrong?
I have two set of checked out files, first set is checked out to "c:\s\u" and other one to "e:\1\2\3" and I want to check in only first set of files.
To do that I am using cmd client with next cmd line:
"D:\Program Files\SourceGear\Vault Client\vault.exe" -user User - password "Password" -host Host -repository "Name" commit "$/s/u" -unchanged checkin
It returns me an error:
<vault>
<error>
$/s/u does not exist in the current change set.
...
But gui client shows that pending change set contains that files.
Where am I wrong?
Hi Dan,dan wrote:The current version of the command line client doesn't allow you check in a single folder recursively - you have to list each file to checkin, or specify that you want to checkin the whole change set.
The ability to checkin one folder recursively will be available in the upcoming 3.0 release.
Is the command line in vs3 going to support a recursive check-out that allows you to specify a wildcard?
I'm using FinalBuilder2 that hooks up to the command-line (rather than the API I believe), and I want to tell it to do a recursive check-out on all project files, dll's, etc in a particular Vault directory.
Thanks
Christian