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. KeyĬomma-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. You can also analyze test code, and for that you need to provide tests binaries and test libraries properties.
If you are not using Maven or Gradle for analysis, you must manually provide bytecode to the analysis. class files are missing, you'll see warnings like this: Class 'XXXXXX' is not accessible through the ClassLoader. java files, please provide compiled classes with property, or exclude them from the analysis with sonar.exclusions property. If not provided properly, analysis will fail with the message: Your project contains. class files are required for java projects with more than one java file. You can discover and update the Java-specific properties in: Administration > General Settings > Java Java Analysis and BytecodeĬompiled.
0 kommentar(er)
