Placing Projects Under Version Control

AccuRev Plug-In for IntelliJ IDEA provides access to AccuRev version control commands within IntelliJ IDEA . The commands executed by the Integration move data between a central source-code repository (a depot) and a personal AccuRev work area (a workspace). AccuRev can manage an IDE project’s files if (and only if) the project’s location on disk is within an AccuRev workspace. It doesn’t matter which is created first, the IDE project or the AccuRev workspace.

Also relevant is this aspect of AccuRev’s data architecture: AccuRev does not automatically version control every file within an AccuRev workspace. For example, version-controlling text-editor backup files would be a waste of resources. Files created in a workspace initially have (external) status. They become version-controlled elements when explicitly processed with the Add to AccuRev Depot command.

Given these facts, it makes sense to consider the following use cases. Before performing any of the procedures, make sure that AccuRev depots and streams have been created and properly configured. These operations cannot be performed within IntelliJ IDEA .

Case 1: An IntelliJ IDEA project already exists and you want to make AccuRev its version control provider

Perform the procedure in the section Making AccuRev the Version Control Provider for an Existing IDE Project.

Case 2: Your sources are already under AccuRev version control and you want to use IntelliJ IDEA for development

If you have access to an AccuRev workspace containing the sources, perform the procedure in Creating a New IDE Project in a Workspace.

If you need to create a new AccuRev workspace containing the sources, perform the procedure in Creating a New Workspace for Sources that are Already Under AccuRev Version Control.

Case 3: Your sources are located in an AccuRev workspace and an IntelliJ IDEA project exists for the sources

Click File > Open Project, navigate to the project file (.ipr), and click OK.