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 46 Next »


This feature is available since Sonar 2.6.


  • Java 1.5 or higher
  • Sonar 2.6 or higher. The server must be up when analyzing projects.



  1. Uncompress the downloaded file into a directory named $SONAR_RUNNER_HOME in the next steps.
  2. Update global settings (database connection, server URL) by editing the file $SONAR_RUNNER_HOME/conf/
  3. You can check the basic installation with opening a new shell and executing the script '$SONAR_RUNNER_HOME/bin/sonar-runner -h'. You should get a message like this :
  4. Set the SONAR_RUNNER_HOME environment variable to the directory $SONAR_RUNNER_HOME where you installed the Sonar Runner
  5. Add the $SONAR_RUNNER_HOME/bin directory to your path.


For each project create a file in the base directory :

Alternatively, you can specify a location using the project.settings property.

For advanced features such as reusing existing unit test reports, you can set advanced parameters in this file or through command-line parameters. 
You can then execute 'sonar-runner' from project base directory to launch a Sonar analysis.


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.


Due to SONARPLUGINS-1024, not possible to set "." as a source directory with Sonar 2.6.


Here the source code of a sample C project.



Release 1.1 (5 issues)


Release 1.0 (1 issues)

Type Key Summary Priority Status Resolution
New Feature SONARPLUGINS-951 Create a Sonar Standalone Runner (In addition to the Maven & Ant Runners) Major Closed Fixed

  • No labels