clearcase

In a base clear case project that I have, the config spec handed to me reads like this: element * CHECKEDOUT element * .../PROJ_1.5.0/LATEST element * .../main/LATEST -mkbranch PROJ_1.5.0 element * /main/LATEST I read up a bit on config specs here at his guide: http://www.philforhumanity.com/ClearCase_Support_17.html It seems to me that in my config spec, the last line has no value. Because element * /main/LATEST is already there on the second last line. Is my understanding correct? VonC That last line is a selection rule stopper : it is a rule which will always be selected if all the other

Sorry if its to naive. I am wanting to write a simple PERL script that will accept two arguments(Here Commit Labels) which are taken as inputs to cleartool command and provides me with a suitable output. My Code: #!/usr/bin/perl $file1 = system('cleartool find . -version "lbtype($ARGV[0])" -print > filename1'); $file2 = system('cleartool find . -version "lbtype($ARGV[1])" -print > filename2'); $file3 = system('diff filename1 filename2 > changeset'); print $ARGV[0]; print $ARGV[1]; print $file3; close filename1; close filename2; close changeset The output now is 3 empty files: filename1

Let's say there is a file called myfile.java. I checked it out and I was working on it. Before checking it in, I have lost my hard drive and I had to get a new hard drive. Next time that I want to check out the file, it says that I can not check out. It was already checked out in the old view which has gone. I have to mention that I am using the option "re-use development stream option". Is there anything I can do to be able to checkout the file once again? You can completely unregister your old view in the vob of that file: that will remove the "checkout" status associated to that file.

I have tried to get the full history of a clearcase vob to parse it and use it with gource to get a visual representation of the changes, but I do not find the right commands to get an easy log history to parse with clearcase2gource python script. I do not use UCM, there are no streams, just plain cleacase. With this command I get elements with @@ in the middle of a path: cleartool lshistory -fmt "Element: %n| Date: %d| User:%u| Operation: %e| Object:%[type]p| SimpleType: %m| OperationKind: %o\n" -all /vobs/vob_name With this command I get elements like this (deleted at some point): Element:

My fonts were delivered to the branch with the command clearfsimport -rec -nset <Source> <target> My problem is: supose in my next deliver I delete 10 files in different folders, I saw that there are many fonts in my first version and now I have fonts from my version1 that were deleted. I need to know how to solve this problem. VonC Looking at clearfsimport , you should consider the -rmname option: For all source-name arguments that are directories, performs an rmname operation on elements that are already in the VOB but are not present in the source directory. If used in combination with

I want to ask what is exactly the derived object in ClearCase and how is work. Additional i want to ask if there is an other program with the same function, because in Git, MKS or in IBM® Rational Team Concert™ i cannot find something similar, is it obsolete ? This is quite linked to dynamic views, which are very specific to ClearCase and not found in other more recent VCS. See " ClearCase Build Concepts " Developers perform builds, along with all other work related to ClearCase, in views. Typically, developers work in separate, private views. Sometimes, a team shares a single view (for

I have this strange hijacked file in my snapshot view. when I undo it, it doesn't go away. Is there a way to un-hijack it. I already tried undo-hijacked but didn't work. I should see .keep file if it unhijacked but didn't see any. Also tried to check out and uncheck out but this file still remains as hijacked. Thanks for any help !! There is usually one case where an hijacked file remains hijacked when you try to cancel it (following " Canceling a hijack "): It is when the file is kept by an handle (it is opened or used by another process). Try to close as many application / processes (or even

I have an eclipsed file in my ClearCase dynamic view. If I use ClearCase Explorer, I see it's eclipsed (the yellow moon icon). If I check the command-line, I see it's eclipsed indeed. When I use ClearTeam Explorer, it does not specify it's eclipsed (no text, icon or something like that). Since I tend to use the new explorer, I'm wondering how it should work on this situation? It can depend on your ClearTeam version ( release notes for 8.0 ), since CM API support for dynamic views The ClearCase CM API now supports dynamic views. For detailed information on API changes, refer to Technote 1566574