To create a build specification with kwgradle:

1. Run gradle clean.
2. Navigate to the directory that contains the build.gradle file. (Skip this step if you specify the file name with the -f option of gradle).
3. Run kwgradle:

   kwgradle —-output /home/klocwork/freemind.out install
   

Continue to Checking your build specification file.

To create a build specification with kwgradlew:

1. Run gradle clean.
2. Navigate to the directory that contains the gradelew file, or for Windows, the gradelew.bat file.
3. Run kwgradlew:

   kwgradlew —-output /home/klocwork/freemind.out install
   

Continue to Checking your build specification file.

To create a build specification with kwmaven:

1. Run mvn clean.
2. Navigate to the directory that contains the pom.xml file. (Skip this step if you specify the file name with the -f option).
3. Run kwmaven install:

   kwmaven —-output /home/klocwork/freemind.out install
   

Continue to Checking your build specification file.

To create a build specification with kwant:

1. Run ant clean.
2. Navigate to the directory that contains the build.xml file. (Skip this step if you specify the file name with the -f option of ant).
3. Run kwant:

   kwant —-output /home/klocwork/freemind.out
   

Continue to Checking your build specification file.

Editing the Ant build.xml file allows you to generate a build specification with greater control over all stages of the build. In this case, you add the exec-listener task to your Ant build file, which will use the Klocwork Ant build listener (KwAntListener) to produce a build file.

To edit the Ant build file and produce a build specification:

1. Edit the Ant build.xml file to add the kwant taskdef and properties after the project description (see example below).
2. Run your Ant build as usual.

Example

 <project name="MyProject" default="dist" basedir=".">
    <!-- Insert the following code -->
    <property name="kwout" location="kwant.out"/>
    <property name="rep.inst" location="full path to the installation directory"/>
    <!-- Included for integration builds -->
    <property name="buildspecUpdate" value="true"/>
    <taskdef name="exec-listener" classname="com.klocwork.kwant.KwAntListener">
        <classpath>
            <pathelement location="${rep.inst}\class\kwant.jar"/>
            <pathelement location="${rep.inst}\class\buildspec.jar"/>
            <pathelement location="${rep.inst}\class\kwutils.jar"/>
            <pathelement location="${rep.inst}\class\log4j.jar"/>
            <pathelement location="${rep.inst}\class\jdom.jar"/>
            <pathelement location="${rep.inst}\class\commons-io-1.4.jar"/>
            <pathelement location="${rep.inst}\class\datautils.jar"/>
            <pathelement location="${rep.inst}\class\buildutils.jar"/>
       </classpath>
    </taskdef>
    <exec-listener/>
</project> 

The output file is saved to the specified location. You can now use the build specification to build the project.

When running in incremental mode (the buildspecUpdate property is set to true), manual integration will only pick up compiled files at build time. Any previously compiled files won't be added to the build specification for analysis. To get those files, you must recompile your project (for example: ant clean build).

For a project that contains .jsp files, you create two build specifications:

• one build specification for the .jsp files, using kwwebappscan. kwwebappscan scans the directory, finds Web application directories that contain .jsp files, and produces a build specification. For full details on this command, see kwwebappscan.
• one build specification for the Java source files, as shown in previous sections

You then use both build specifications when you run a Klocwork analysis on the project.

Open the build specification you just created and confirm the existence of jconfig and jcompile lines. For more details on the format of this file, see Build specification file format .

If the jconfig and jcompile lines are present, you are ready to move to the next step: Running the Java integration build analysis.

If your build specification file doesn't contain jconfig or jcompile lines, here are a few things you can try:

• Make sure your project contains Java source files.
• Look at alternate integration methods. See the alternate methods described in this article.

You need to update or create a new build specification in the following situations:

• if source files are added or removed
• if build settings are changed

If you reuse an existing build specification or try to modify it manually in these situations, the analysis results will not be accurate.

• If you're analyzing your integration project, go to Running the Java integration build analysis.
• If you're analyzing a desktop project, go to Fixing issues before check-in with Klocwork Desktop Analysis and pick your development environment.