Apply keyword expansion for existing files checked in

derekmcloughlin · Post by **derekmcloughlin** » Thu Feb 17, 2005 9:02 am

Hi,

When we migrated from VSS to Vault, we forgot to switch on keyword expansion in Vault Admin.

I've checked the setting for enabling keyword expansion, but would now like to apply the expansion to all files in the repository.

I can't simply check out and then check-in, because Vault will only check-in if changes have been made.

Is there any way to force a check-in even if there are no changes? That way, the old values of the expanded keywords will be replaced by new values.

Derek.

dan · Post by **dan** » Thu Feb 17, 2005 9:45 am

Go to Tools->Options->Check In, and you can change the value under "Check In unchanged files" to check them in rather than undo the checkout.

mlippert · Post by **mlippert** » Thu Feb 17, 2005 10:39 am

That's interesting.

I made a concious decision to do the opposite. It made sense to me to made sure that keyword expansion was off during the VSS Import so that the files in Vault would exactly match the files as the existed in SourceSafe.

I then turned keyword expansion back on so that all new files changed and checked into Vault would have their keywords reflect their new status.

These are pretty much the only keywords we use though:

Code: Select all

//*   $Workfile:: StdAfx.h                                                   $
//*   $Revision:: 5                                                          $
//*     $Author:: Mlippert                                                   $
//*       $Date:: 4/01/04 12:27p                                             $
//* $NoKeywords::                                                            $

derekmcloughlin · Post by **derekmcloughlin** » Thu Feb 17, 2005 10:53 am

Dan,

I tried your suggestion, but on the check-in, though the revision number went from 3 to 4 in a sample file, the $Revision keyword in the file didn't change.

Derek.

derekmcloughlin · Post by **derekmcloughlin** » Thu Feb 17, 2005 10:54 am

I should mention that this is version 2.0.6

bfinney · Post by **bfinney** » Thu Feb 17, 2005 3:18 pm

Yeah... it looks like there's a bug where non-modified files' keywords are not updated. It's been logged, but for the short term, the only way around this is to make a trivial change to each affected file.

Sorry for the bad news.

SourceGear Support