Prevent Downgrade of Non-versioned Files

[sgoldstein]

In a merge module, we have a number of files which by nature are not versioned - xml files, text files, jar files. Is there a common mechanism that can be used to prevent downgrade of these files?

The only work around that I've found so far is to set the REINSTALLMODE property to "p" on the command line. It would be nice, however, to have an automated way.

Thanks.

Scott

[Stefan_Krueger]

Companion files

[sgoldstein]

Thanks for the reply. I've seen the companion files feature. I think it will work well for text files, but not for jar files. Jar files are essentially libraries that by nature have their own version. However, they don't use the standard Windows file versioning mechanism.

[Stefan_Krueger]

A "dummy" DLL included just for file versioning purpose could make companion files work in this case. It's the best solution I can think of right now.