Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 61 Next »

This bootstrapper is recommended to run analysis on non-Java projects.


Table of Contents


You must have previously installed the Sonar Runner analyzer.


For each project a file must be created in the root directory of the project. This project configuration file must contain all properties required by Sonar to analyze the project:

Then the command 'sonar-runner' or 'sonar-runner.bat' (windows) must be executed from the project base directory to launch the Sonar analysis. That's it!

If a file can't be created in the root directory of the project, there are two alternatives :

  • Either properties can be specified directly through the command line. Ex: 'sonar-runner -Dsonar.projectKey=myproject -Dsources=src1 ...'
  • Or the property 'project.settings' can be used to specify the path to the project configuration file. Ex:  'sonar-runner -Dproject.settings=../'.

For advanced features such as reusing existing unit test reports, any Sonar advanced parameters can be defined in this project configuration file or through command-line parameters. 


If you get an java.lang.OutOfMemoryError, you can set the SONAR_RUNNER_OPTS environment variable, like this in *nix environments:

On Windows environments, avoid the double-quotes, since they get misinterpreted, turning the two parameters into a single one.

Sample Project

Here is the source code of a sample C project analyzed with the Sonar Runner.

Advanced properties

Here are some advanced optional properties that can be used for the Sonar Runner:

  • No labels