Description of the project.
Comma-separated paths to directories containing binaries (in case of Java: directories with class files).
Comma-separated paths to directories containing tests.
Comma-separated paths to files with third-party libraries (in case of Java: JAR files). Pattern can be used.
Note that * wildcard character is not supported for directories (only for files).
This property is used by rule engines during issues detection (mainly SonarQube engine and FindBugs engines which rely on bytecode). Having the bytecode of these libraries allows to get more information on coupling, possible null parameters when calling external APIs, etc. and thus getting more accuracy during issues detection.
Analysis mode. See Concepts.
Encoding of source files. Example of values: UTF-8, MacRoman, Shift_JIS. This property can be replaced by the standard property
The list of available encodings depends on your JVM. See http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html.
Sometimes, for security or other reasons, project sources must not be stored and displayed.
When starting to analyze a new project, you may want to feed your SonarQube instance with the quality snapshots of the last versions of this project. In order to get some information on quality trend over the last versions.
When moving from one database engine to another, it is highly recommended (even mandatory) to start from a fresh new database schema. In this case, you will lose your whole history. So, you may also want to feed the new SonarQube instance with some historical data.
To answer those use cases, you can use the
The process is the following:
Note: first analyze the latest version and then move in chronological order to the newest one.
Exclude files from analysis. See Project Administration for more details. This page also details
Some project modules should not be analyzed and consolidated with global project measures, for instance samples, integration tests or generated code.
Comma-separated list of the modules to analyse, all other modules are automatically ignored. Be careful: the root project must be added to the list.
Manage SCM branches. Two branches of the same project are considered as different projects in SonarQube.
Through the web interface, you can define as many quality profiles as you want and you can easily associate one of these quality profiles to a given project.
Default profile for the given language
To skip the computation of design metrics and dependencies.
Currently only available for Java.
When SonarQube needs a Maven phase or goal to be executed prior to the analysis, this parameter can be used. For example
Dynamic analysis relates to unit tests. By default (
See the Code Coverage by Unit Tests tutorial for details and examples.
To set the working directory for the analysis triggered wit the SonarQube Runner or the SonarQube Ant Task (versions greater than 2.0).
Path must be relative and unique for each project.
Beware: the specified folder is deleted before running each analysis.