This topic contains troubleshooting information
for the code review application.
FAQs: Frequently asked questions
- Why is the code review application generating
so many different types of data files? How can I cause it to generate
only certain types?
The code review application always generates
all the types of data files that are registered with Eclipse, and
that apply to the programming language or languages in which the specified
source code files are written.
- Why does a strange URL appear in the output information?
Example:
[url]http://server:9090/rsar/reports/20121004_162226/[/url]
See Using the output information.
Troubleshooting
- When I run the code review application, no output
information is written to standard output. How can I get the application
to produce this information?
Follow these steps:
- If you are using Windows:
- Verify that you are using the parameter -verbose.
- Verify also that you are redirecting standard output to an output
file on the command line. See the descriptions of the -verbose parameter
and the output file.
- If you are using Linux,
or if you are using Windows but
have already done the checks described in the previous bullet, here
are some of the reasons why all or part of the output information
can be missing:
- A path that you are passing as a parameter to the application
is not correct.
- The project or directory that you have specified does not contain
any source code files.
- The rules in the rule file do not apply to any of the source code
files that you are analyzing.
- Try using the sample script to run an analysis similar to the
one that is not working for you. Turn on the -debug
option of the sample script to have output information printed to
the screen. If the sample script produces the correct output,
compare it to your invocation to spot the problem.
- Why do the paths in my output files contain prefixes
such as "genericProject_" and "analyzedAsJava_? See Temporary
projects created with the -directory parameter.