sonar.profileparameter via command line for a specific project, it will not be stored in the database. Then, a local analysis in Eclipse will be run against the default quality profile.
JDBC Connection URL
Prior to SonarQubeTM 3.2: jdbc:derby://localhost:1527/sonar
User for the JDBC Connection
Password for the JDBC Connection
The project key that is unique for each project.
Name of the project that will be displayed on the web interface.
The project version.
Set the language of source code. If a plugin allows to analyze another language, the associated source code analyser can be activated with this property.
Comma-separated paths to directories containing sources.
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 SonarQubeTM 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.
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.
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
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 SonarQubeTM.
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 SonarQubeTM 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, 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
See the Code Coverage by Unit Tests tutorial for details and examples.
To set the working directory for the Sonar Runner or the Sonar Ant Task (versions greater than 2.0).
Beware: the specified folder is deleted before running each analysis.
Increasing HTTP timeouts of requests to server. The Maven plugin executes some HTTP requests to the server. Two timeouts makes the call fails if the server connection is too slow. In such a case the timeouts can be increased from Maven properties.
respectively 30'000 and 60'000 milliseconds
|Display logs to know where time is spent|
|Display all the SQL requests executed on batch side|
|Display the result of all SQL requests executed on batch side|
|Activation of the DEBUG mode on batch side|