legacy files seem to behave wrong for multi versions

[rjfioravanti]

I am having problems with the deletion of legacy files for my patch. My setup is a little complicated but I will try to simplify the scenario

Say I have version
1, 2, 3, 4, 5

The file "foo" exists in version 2 and 3. So it does not exist in version 1, and in versions 4 and 5 it is a legacy file that should be deleted.

Now I want to create a patch just up to version 3 (say versions 4 and 5 are too unstable for a certain client). I create a patch that includes only versions 1, 2 and 3. I am looking at the log file and it seems to flag the file "foo" as a legacy file. It scans versions 4 and 5 for legacy files even though I did not select them to be included in the build.

When I apply the patch to an instance of version 1, it patches most things properly but does not add the file "foo" (because it thinks it is a legacy file?)

If I reorder my versions (Versions -> Organize) and reorder them to be 1, 2, 4, 5, 3.. then my problem is solved

Is this a bug or am I doing something wrong?

[Lorne]

Now I want to create a patch just up to version 3 (say versions 4 and 5 are too unstable for a certain client). I create a patch that includes only versions 1, 2 and 3. I am looking at the log file and it seems to flag the file "foo" as a legacy file. It scans versions 4 and 5 for legacy files even though I did not select them to be included in the build.That is a known bug that has been fixed for the next service release (3.0.2.0). I'm not sure when 3.0.2.0 will be released.

In the meantime one workaround is to create a separate project and remove the versions from that project (instead of turning those versions off in the build list).

Sorry for any inconvenience this may have caused.