Analysis Parameters

Description of the project.
Set through <description> when using Maven. 

Comma-separated paths to directories containing binaries (in case of Java: directories with class files).
Not compatible with Maven: binaries retrieved from default location for Java Maven projects. 

Comma-separated paths to directories containing tests.
Not compatible with Maven: tests retrieved from default location for Java Maven projects.  

Encoding of source files. Example of values: UTF-8, MacRoman, Shift_JIS. This property can be replaced by the standard property project.build.sourceEncoding in Maven projects.

The list of available encodings depends on your JVM. See http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html.

System encoding

sonar.importSources

Sometimes, for security or other reasons, project sources must not be stored and displayed.

true

since 1.5

It becomes quickly necessary to input historical data and to highlight some events. It is possible by going for example in a subversion tag and use the sonar.projectDate option. Format is yyyy-MM-dd, for example 2010-12-25.

Current date

since 1.5

sonar.exclusions

Exclude files from analysis. This property is usually set in the page Settings of the project. It's a comma separated list of wildcard patterns. Paths are defined from the source base directory. Example: com/mycompany/*.java,**/*Dummy.java.
Complete documentation on the Sonar web interface: go to MyProject > Exclusions.
To exclude a module (Maven module, C# module, etc.), you have to use the sonar.skippedModules property. 

since 1.8

sonar.skippedModules

Some project modules should not be analyzed and consolidated with global project measures, for instance samples, integration tests or generated code.
If a module's artifactId differs from its module name (the directory name) : it is the artifactId that should be use instead of the module name. Format is a comma-separated list of modules: module1_toexclude,module2_toexclude.

since 1.5

sonar.includedModules

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.
If a module's artifactId differs from its module name (the directory name) : it is the artifactId that should be use instead of the module name.

since 2.2

Manage SCM branches. Two branches of the same project are considered as different projects in Sonar.

since 1.10

sonar.profile

Through the Sonar web interface, you can define as many quality profiles as you want and you can easily associate one of this quality profile to a given project. You can also make this association by using the property "sonar.profile".

Default profile for the given language

since 1.6

sonar.skipDesign

Deactivate Java bytecode analysis. Since Sonar 2.0, the java bytecode is analyzed by Sonar in order to extract dependencies between packages and files. Those dependencies are used for instance to display the DSM (Dependency System Matrix). This bytecode analysis can be deactivated.

false

since 2.0

sonar.phase

Run maven phase or goal prior to analysis. When Sonar needs a phase or maven goal to be executed prior to analysis, this parameter can be used. For example sonar.phase=generate-sources. This property is used only for Maven analysis.

since 1.10

sonar.

Java Version of the Source Code. This property is not used by the Sonar core but can be used by Java Sonar plugin like the PMD plugin. 

1.4, 1.5, 1.6 since 2.10. 1.7 since 2.12

since 2.6

sonar.java.target

Target Java Version of the Source Code. This property is not used by the Sonar core but can be used by Java Sonar plugin like the Clover plugin.

1.4, 1.5 since 2.10

since 2.6

dynamicAnalysis

Dynamic analysis relates to unit tests. By default, those unit tests are executed but you can optionally decide to do only static analysis or to reuse existing reports which have been previously generated. Possible values are true, false, reuseReports.

See

the Code Coverage by Unit Tests tutorial for details and examples.

true

since 1.7

sonar.surefire.reportsPath

The absolute or relative path of the surefire reports directory. Used only if sonar.dynamicAnalysis is reuseReports.

See the Code Coverage by Unit Tests tutorial for details and examples.

since 1.7

sonar.jacoco.reportPath

The absolute or relative path of the jacoco report file. Used only if sonar.dynamicAnalysis is reuseReports.

See the Code Coverage by Unit Tests tutorial for details and examples.

since 2.12

sonar.cobertura.reportPath

The absolute or relative path of the cobertura xml report file. Used only if sonar.dynamicAnalysis is reuseReports.

See the Code Coverage by Unit Tests tutorial for details and examples.

since 1.7

sonar.clover.reportPath

The absolute or relative path of the clover xml report file. Used only if sonar.dynamicAnalysis is reuseReports.

See the Code Coverage by Unit Tests tutorial for details and examples.

since 1.7

The absolute or relative path of the jacoco report file for integration tests.

See the Code Coverage by Integration Tests tutorial for details and examples.