Clearcase: Branch points ancestorlinks aren't being created when the branches are processed in the wrong order

FishEye indexes ClearCase repositories on a branch-by-branch basis. This causes problems for branchpoints. FishEye correctly detects the branchpoint, but fails to set up the link between the ancestor when that branch hasn't been processed yet and as a result it hasn't created an entry for the parent in the infdb index.

There is no way to force processing to be done in the 'correct' order, because branching is a per-file operation in ClearCase. As a result, some files may be branched branch1 > branch2, while other files are branched branch2 > branch1. The fix is to change the processing model from per-vob-per-branch to per-vob and process all events/activities sorted by date.