accurev Questions

By Riyaz Ahmed - July 15, 20132 Answers

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


By New Name - December 17, 20122 Answers

I am trying to set up a automated promote from a non workspace stream to its parent on a daily basis. What is recommended?

1. To create an xml and use promote?

2. To directly promote everything from pending?

What difference it would make if we use xml's?

Note: We have change package trigger on. My plan is to promote all pending issues.

Thank you.

As a long time user of Eclipse+SVN, we recently started using AccuRev as SCM tool. Prior to any commits (keeps) I generally switch to the Team Synchronizing perspective to check my changes. From there I then perform a keep operation.

Whilst this works fine for the first keep (from backed), any subsequents edits are differenced against the backed version, not latest kept.

I don't prompt that often, but do lots of keeps. Is it possible to change the behaviour of the Team Synchronizer?


Using version 2012.1.0 of Eclipse Plug-in for AccuRev, on Eclipse 3.7.1

By bbuttolph - February 21, 20112 Answers

Quiz: At any point in time, Diff-against-Backed and Revert-to-Backed refer to the same version.

a) True. The term "Backed" is used by both operations to refer to the version you started with, meaning from the time of your last update or promote operation.

b) False. Diff-against-Backed refers to the latest version in the backing stream regardless of your last update or promote operation. The version you're diffing against could be a newer version in the backing stream.

The correct answer is 'b'. AccuRev uses the term "Basis version" to refer to the version in the backing stream since your last update or promote operation. Hence, there's the option "Diff-against-Basis" to use this version. However, there is no Revert-to-Basis. Assuming there is a newer version in the backing stream, if you Diff-against-Basis and want to have that version in your workspace, you must Revert-to-Backed. Huh?

I realize that Diff is an exception to the rule that all workspace commands are relative to the last update or promote operation and that a Revert-to-Backed using the Diff meaning would not result in what most users would want. However, when you're trying to explain the terminology to a new team member new to AccuRev, amidst the glazed looks and smirks you invariably wind up apologizing for the complexity and just hope that they eventually "get it".

Would simply changing the menu option Revert-to-Backed to Revert-to-Basis be the answer, or is there a valid reason for this inconsistency?


Thanks in advance for your help!

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.