Workaround for Vault Nant task <vaultgetfile />

mitch.wheat · Post by **mitch.wheat** » Wed Jun 07, 2006 9:01 pm

Hi

I'm investigating a workaround for the Vault NAnt task <vaultgetfile /> not attempting a merge and overwriting any checked out files. Is there any known way using the Vault NAnt tasks to determine if any files are checked out so that I can abort when run on a developers machine?

(Using vault 3.1.

Regards,
Mitch Wheat

mitch.wheat · Post by **mitch.wheat** » Wed Jun 07, 2006 9:46 pm

That should be 3.1.8 (not sure where that smiley came from!)

lbauer · Post by **lbauer** » Thu Jun 08, 2006 6:13 am

The forum software thinks "8" followed by ")" is the "Cool" emoticon.

I'll leave it to our NAnt specialist to respond to your other issue.

dan · Post by **dan** » Thu Jun 08, 2006 8:28 am

I'm not the Nant expert, but take a look at the answer to this post http://support.sourcegear.com/viewtopic ... 5172#25172

Nant Vault tasks don't overwrite modified files as far as I know (unless your Get Latest option is set to overwrite). They do overwrite files that are old but checked out. Let us know if this is the issue you are seeing.

ian_sg · Post by **ian_sg** » Thu Jun 08, 2006 10:30 am

Dan's answer here with respect to the Nant getfile task isn't quite right. Because Nant is a build tool, we set the defaults to reflect the most common desired behavior in a build script, which in this case means that it does always overwrite. An option to change this default will be included in the Vault 3.5 release. There are more details here: http://support.sourcegear.com/viewtopic ... 5192#25192.