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 32 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. Download the Java Runner and uncompress the downloaded file into a directory.
  2. Set the SONAR_RUNNER_HOME environment variable to the directory where you installed the Java Runner. On some operating systems, the startup scripts can guess SONAR_RUNNER_HOME (Unix dialects), but it is better to not rely on this behavior
  3. Add ${SONAR_RUNNER_HOME}/bin (Unix) or %SONAR_RUNNER_HOME%/bin (Windows) to your PATH
  4. Update global settings (database connection, server URL) by editing the file ${SONAR_RUNNER_HOME}/conf/
  5. You can check the basic installation with opening a new shell and typing 'sonar-runner -h'. You should get a message like this :


For each project create a file in the base directory :

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: Java heap space and until SONARPLUGINS-1004 is fixed, you need to edit bin/sonar-runner(.bat) and add -Xmx1024m to the command line.


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


com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.
  • No labels