tags:

views:

164

answers:

0

I've been hired to audit multiple versions of a large application's source code repository. In particular, I want to verify whether certain components of newer versions of the system existed (or in some cases did not exist) in previous versions of the system. The company has been around for over a decade and there are about 60000 revisions in the repository.

There have already been some posts here about tools to help one visualize diffs and changesets on a line-by-line basis, but I'm looking for something more intelligent than that. In particular, I would like the system to be able to track changes classes over time regardless of what file they are in. For example, in older versions of this code a lot of the important classes were contained in a single file, and then at some later date the developers (correctly) broke them out into separate files.

I've tried using FishEye, but the repository was so massive (25GB!) that FishEye never finished its initial scan. This repository is also not set-up in the de-facto way (i.e., separate directories for branches/trunk/tags -- it was originally imported from VSS so that might be a problem).

Does anybody have any suggestions for tools that might be useful for this task? I am guessing that I'm just going to have to slug through this myself, but I wanted to see if there was anything out there.