merge of directories in clearcase

It depends on the history of the two versions of a directory being merged from one branch to another:

if one version has removed files (i.e. has less files than the other version)if said version is merged onto the other,

the resulting version will have less files than initially shown in the view.

That could be because:

that view is not the one used for the mergethat view is the correct one, but with an eclipsed or hijacked content (privates files replacing versioned files)

In any case, what would help in the mentioned view is:

a 'cleartool ls' in the directory mergeda 'cleartool ls' in the parent directory of the directory merged.

The output of those two commands would help to confirm the exact status of the files merged within that directory, as well as the status of the directory itself.

View the original article here

RSA 7.5 + Clearcase 7.0 issue: manual merge resulting in loss of stereotype

This question is not answered.

Posts: 1
Registered: Nov 26, 2010 12:46:15 PM RSA 7.5 + Clearcase 7.0 issue: manual merge resulting in loss of stereotype
Posted: Nov 26, 2010 01:18:37 PM I'm using Rational Software Architect 7.5 + Clearcase 7.0 to handle a fragmented uml model. When I have two or more users working on the same fragment, and one of them need to reorder attributes(stereotyped) of a stereotyped Class, after merging the stereotypes are lost. Do you have any idea how to solve this issue?

Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular type of content or application that you're viewing.

My tags shows your tags for this particular type of content or application that you're viewing.

Use the search field to find all types of content in My developerWorks with that tag. Use the slider bar to see more or fewer tags. Popular tags shows the top tags for this particular type of content or application that you're viewing. My tags shows your tags for this particular type of content or application that you're viewing.MoreLess 

View the original article here

Clearcase: How do I merge in a specific file from one view, into another, to avoid the Evil Twin scenario?

I no longer have access to a clearcase environment, so this is from memory, but what you want is to link in a version from another branch into the one that you are working with.

Let's assume that you have a file new_file that have been added on the branch new_feature (the latest version is new_file@@/main/new_feature/5) which you want to merge/bring into the branch maintenance.

prompt>cleartool checkout -nc .checking out some_dir@@/main/maintenance/2...prompt>cleartool ln .@@/main/new_feature/LATEST/new_file/main/new_feature/5 ....prompt>cleartool ci -c "linked in .@@/main/new_feature/LATEST/new_file/main/new_feature/5"prompt>

The commands above are probably not 100% correct, but should give you the idea. You want to use cleartool ln to avoid evil twins, because that will bring in a version from the already existing element (i.e. not creating a new twin).

View the original article here

Re: Merge Manager question

Posts: 208
Registered: Oct 31, 2006 04:24:09 PM Merge Manager question
Posted: Oct 06, 2010 06:06:09 PM Hi guys,

When performing an ordinary merge from a development branch to the main branch, Merge Manager skips the merge of directory versions that are identical to those on the main branch, which is of course perfectly normal.

cleartool findmerge . -fversion -c "Comment" -merge -abort -nzero

However, when a new directory element was created on the development branch, and no file elements were added to it, the version that you're left with for future development is the zero version on the main branch. Merge Manager does not merge the 1 version on the development branch back to the main branch since they're identical.

This does not create any problems at all, apart from being stuck with a dangling branch that was never merged. Also, I don't like zero versions. I would prefer to merge these 1 versions from the development branch anyway, so that we'd have a 1 version on the main branch also, and a merge arrow to boot. Is there a way to accomplish this automatically? I currently resort to merging them manually when this happens (fortunately it doesn't happen all that often).

Thanks,

Jozef

Posts: 2
Registered: Oct 08, 2010 09:22:33 AM Re: Merge Manager question
Posted: Oct 08, 2010 02:06:42 PM   in response to: Jozef's post if it bothers you that much you could write a script and run it after you run the merge. Have the script find the most recent directory version on the branch and see if it has a merge hyperlink. If it doesn't you can either print it out or have the script run a merge.
Posts: 208
Registered: Oct 31, 2006 04:24:09 PM Re: Merge Manager question
Posted: Nov 08, 2010 05:05:58 PM   in response to: DanEngland's post Thanks - actually, it does create a problem because the main branch is set up here as the Production branch. The production labels are moved down from the development branch. I only move down labels from versions that have a merge arrow, which those empty directories do not have. This results in the directory becoming invisible when work starts on the next development branch. The same problem happens when a developer forces an identical checkin by the way, because Merge Manager does not merge those either.

Here's the commands that merge these "problem" versions. They're located in BuildForge steps, which explains all those additional %s and "s.

:: check out the version on the main branchcleartool find . -version "version(\main\${BRANCH_TO_BE_MERGED}\${LABEL_TO_BE_MERGED}) && !merge(\main\${BRANCH_TO_BE_MERGED},\main)" -exec "cleartool checkout -comment """Merge $LABEL_TO_BE_MERGED to main""" "%%%CLEARCASE_PN%%%"":: merge the versionscleartool find . -version "version(\main\${BRANCH_TO_BE_MERGED}\${LABEL_TO_BE_MERGED}) && !merge(\main\${BRANCH_TO_BE_MERGED},\main)" -exec "cleartool merge -to "%%%CLEARCASE_PN%%%" "%%%CLEARCASE_XPN%%%"":: checkin all checkedout versions on the main branch that have a merge arrow from the development branch that was mergedcleartool find . -version merge(\main\$BRANCH_TO_BE_MERGED,\main) -print | find "\main\CHECKEDOUT" >temp.txtFOR /f "delims=@@" %%D IN (temp.txt) DO cleartool checkin -identical -ptime -nc "%%D"

Use the search field to find all types of content in My developerWorks with that tag.

Use the slider bar to see more or fewer tags.

Popular tags shows the top tags for this particular type of content or application that you're viewing.

My tags shows your tags for this particular type of content or application that you're viewing.

Use the search field to find all types of content in My developerWorks with that tag. Use the slider bar to see more or fewer tags. Popular tags shows the top tags for this particular type of content or application that you're viewing. My tags shows your tags for this particular type of content or application that you're viewing.MoreLess 

View the original article here