version control Questions

How do I configure AccuRev so that i can do automatic merge of simple conflicts

In case 2 developers promote the same class but their changes can be easily resolved by AccuRev no action should be required from the developers in order to make more soft the process

thanks

I am using the JHSDK jar available in ths installation directory of CA to write a java program for an automation project.

I am using the below Java code to select the packages from ACEDEV13.06.00.00 from SW Development view and promoting it to next stage 'Integration Test(AIT)'.

Java Code:

JCaContext context = harvest.getContext();

boolean approve = context.setApprove("Approve"); //Exception @ this line is E0309000d: ERROR: Could not get Process.

boolean promote = context.setPromote("Promote");

//Setting the Approval

CaApprove jcaApprove = context.getApprove();

jcaApprove.setApprove(true);

jcaApprove.setDescription("Approved Desc");

jcaApprove.execute();

//Setting the Promote

JCaPromote jcaPromoteObj =  context.getPromote();

System.out.println(" getToStateName "+jcaPromoteObj.getToStateName());

System.out.println(" getToStateObjId "+jcaPromoteObj.getToStateObjId());

jcaPromoteObj.execute();

Exception I get :

com.ca.harvest.jhsdk.hutils.JCaHarvestException: E03090027: ERROR: Could not get Approve Process from Context.

com.ca.harvest.jhsdk.hutils.JCaHarvestException: E03090010: ERROR: Could not get Promote Process from Context.

Do I need to set any mode to context or harvest object to make the Promote process to work. Kindly help me with this.

I am getting ready to install it on my laptop.

Hello,

Our VOB is of size size 52GB, 10years old, mounted on Solaris OS and using by 400 Users. From the past One Year, we observed that VOB elements are keep on corrupting with "^D" or "text_file_delta" error. We are unable to do diff with predecessor version, not able to make Builds because of corrupted files. Even we are unable to count Source Lines of Code also. I forgot to mention that, we are using ClearCase ver.6.0.

Last 8 months back, we raised a PMR, IBM resolved some file elements using "checkvob" and by remotely accessing they used some IBM scripts to solve the issue. Finally, by the end of March. We and IBM Technical Support Engineers resolved all corrupted file elements issue. Recently, we observed that 2 (two) of the files got corrupted again and VOB is not in Sync with two of our replicas. Problem started again.

Please let me know, why VOB file elements corrupts often? Is it because of, if any user uses some third party tools for his Coding/Development in VOB? We CMs follow strict polocies, some of the file elements are not even loading into VOB (Snapshot views), saying "size got exceeded". This became a big mess for us. Now, Developers are making Builds by hijacking the files. We know that, this is not a Good Practise. Please someone of you can help us in this regard. PFA, VOB Errors. Thanks in advance!

Best Regards/Sebastian