Format of the build specification file for Java projects
The Klocwork build specification for Java projects, called kwinject.out by default, is a semicolon-separated text file containing the following information about the Java source files in your Klocwork project:
The first field of each line is a tag to identify the type of line. The possible tags are as follows:
version lineThe version line is used to define the build specification format version. It must be the first line in the build specification. Only one version line may appear in a build specification. Example version line:
version;108 Version 1.4 or later indicates that the build specification was generated using a source encoding of UTF-8, allowing multibyte characters (for example, Japanese). To ensure that kwbuildproject processes the build specification with UTF-8 encoding, the version must be version;104 or later.
jconfig lineThe jconfig line is used to identify Java compiler options — the Java version and default classpath. Example jconfig line: On Unix
jconfig;/space/testing/java/jdk1.7.0_25/bin/javac;-classpath;/space/testing/java/jdk1.7.0_25/jre/lib/resources.jar:/space/testing/java/jdk1.7.0_25/jre/lib/rt.jar;-source;1.7 On Windows
jconfig;c:\program files\java\jdk1.7.0_67\bin\javac.exe;-classpath;c:\program files\java\jdk1.7.0_67\jre\lib\resources.jar%3Bc:\program files\java\jdk1.7.0_67\jre\lib\rt.jar;-source;1.7 There are three fields:
jcompile lineEach jcompile line is used to track Java source file compilation. Example jcompile line:
jcompile;/space/testing/java/jdk1.7.0_25/bin/javac;/space/testing/run/scripts/kwinject/javac/basic/A;a.java The fields are:
jar lineEach jar line is used to track jar execution, in other words, how .jar files are created. Example jar line:
jar;/space/testing/run/scripts/kwinject/javac/basic/A.jar;/space/testing/run/scripts/kwinject/javac/basic/A/A.class The fields are:
|