Question

I baselined a stream this morning, but someone made changes to a couple files that they did not want included in the baseline.

I used the Version Tree to move the label from the newest version to the previous version. (First, was this wrong?)

I then delivered that baseline to a stream in another project. It works fine, and all the correct versions of the files came over. However, now the file in view is version 22, and there is a version 23 that I am not able to see. (I would like to see the newer version, even though I did not want that included in the baseline.) Is there a way to make the view show the latest version of the file?

Note: I tried making a new baseline, but ClearCase included version 22 in the baseline instead of version 23…

Answer 1

The correct course of action, when a Baseline doesn’t reference the right content, is:

• to fix that content (delete as in “cleartool rmname” the files you don’t want to see, checkout/checkin the files you want to fix, creating new versions)
• make a new baseline (you can take the same name, or ‘title’: ClearCase will generate a different baseline id based on that name: BLNAME.xxxx: see “What is the difference between Full baseline and Incremental baseline in Clearcase UCM?“)

Moving a label is not a recommended solution (it is actually supposed to be impossible if that label is linked to a Baseline)

You then deliver that new baseline to any other Stream you want.
But if the source Stream has some new version, then you will need to make another baseline including said new version, and deliver that new baseline, in order for your destination project to see and reference it.