For example, for a Java 8 project, by setting it as follow: =/usr/lib/jvm/jdk1.8.0_211 Turning issues off When setting, you need to provide the path to the JDK directory used by the project being analyzed, if different from the Java runtime executing the analysis. Not setting this property, while it would have been required, usually leads to inconsistent or even impossible-to-fix issues being reported, especially in relation with native JDK classes. By doing this you'll specify which JDK classes the analyzer must refer to during the analysis. If it is your case, and you are NOT using Maven or Gradle, you will need to set the property manually (see below). This case is normally automatically handled when using Maven or Gradle, as well as with any flavor of SonarLint. The most common case is to run the analysis with Java 11, while the project itself uses Java 8 or before for its build. In some situations, you might have to analyze a project built with a different version of Java than the one executing the analysis. Wildcards can be used: =directory/**/*.jarĪndroid users, Jack doesn't provide the required. (For example, this should include the junit jar). Wildcards can be used: =path/to/Library.jar,directory/**/*.jarĬomma-separated paths to directories containing the compiled bytecode files corresponding to your test filesĬomma-separated paths to files with third-party libraries (JAR or Zip files) used by your tests. Comma-separated paths to directories containing the compiled bytecode files corresponding to your source files.Ĭomma-separated paths to files with third-party libraries (JAR or Zip files) used by your project.

Source code java example