Skip to end of metadata
Go to start of metadata

If you are not using Maven, the way to provide bytecode varies by version of the Java Plugin.

You can also analyse test code, and for that you need to provide tests binaires and test libraries properties.

KeyDescriptionVersion
sonar.java.test.binariesComma-separated paths to directories containing the compiled bytecode files corresponding to your test filesFROM 3.2
sonar.java.test.libraries

Comma-separated paths to files with third-party libraries (JAR or Zip files) used by your tests. (For example, this should include the junit jar).
Wildcards can be used :

sonar.java.test.libraries=path/to/specific/Library.jar,path/to/libs/*.jar,directory/**/*.jar
FROM 3.2
sonar.java.binaries

Comma-separated paths to directories containing the compiled bytecode files corresponding to your source files.

Since 4.12, analysis will fail with the message :

Please provide compiled classes of your project with sonar.java.binaries property

FROM 2.5

REQUIRED SINCE 4.12

sonar.java.libraries

Comma-separated paths to files with third-party libraries (JAR or Zip files) used by your project.
Wildcards can be used :

sonar.java.libraries=path/to/specific/Library.jar,path/to/libs/*.jar,directory/**/*.jar
FROM 2.5
sonar.binariesComma-separated paths to directories containing the compiled bytecode files corresponding to your source filesBEFORE 2.5
sonar.libraries

Comma-separated paths to files with third-party libraries (JAR or Zip files).
Wildcards can be used :

sonar.libraries=path/to/specific/Library.jar,path/to/libs/*.jar,directory/**/*.jar
BEFORE 2.5
  • No labels