Prerequisites for running code reviews

When you choose the code base to run a code review on, the code must meet certain prerequisites; most importantly, all files in the code base must be compilable when you run the review.

Note the following prerequisites when running a code review, and the problems that can occur if they are not met:

The following prerequisites apply to the J2EE Best Practices code review only:

Caveats

After you satisfy the prerequisites and are ready to run a code review, some caveats apply in certain situations.

Avoiding multiple files with the same Java path: When you run certain code reviews on the workspace, the review does not cover multiple files with the same Java path even if the files are in different projects. This behavior applies to code reviews or rules that require heavy system processing: Consequently, it is better to avoid multiple files with the same Java path.

Example: Suppose the workspace contains the RED_Examples project and the BLUE_Examples project. Both projects contain the Color package which includes the bright.java file. When you run a code review on the workspace, the review covers one bright.java file only. You can review the code in both files by not having two files with the same path, such as renaming them to brightr.java and brightb.java.

If the workspace does have multiple files with the same Java path, you can run a code review that covers the multiple files by setting up the workspace in the following way:
Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.