JCov Tool Build Instructions

This page describes how to build the JCov tool binary. Some notes before you get started:

• In order to contribute code to the project you must have a contributor role. See OpenJDK Governance for information about the different community roles.
• For a description of how the JCov tool repository is organized, read JCov Tools Repository Structure.
• The JCov Tool Developer's Guide describes how the source code is organized and provides important information for developers who want to modify the code.
• The JCov Tool Source Code Description describes how the JCov tool source code is organized.

Table of Contents

Requirements

The JCov tool build requires the technologies listed in the following table.

Checking out the source

The JCov tool repository is located on OpenJDK servers, in the CodeTools Project.  It is stored in mercurial vcs, and can be uploaded from mercurial via the following command:

  % hg clone http://hg.openjdk.java.net/code-tools/jcov

Configure and Run the Build

The following steps describe how to build SigTest tool. These instructions assume that your SigTest tool local working copy is named sigtest.

1. Set up and configure the JDK 5.0.
   • Download and install the JDKs.
   • Set the environment variable JAVA_HOME to point to the JDK 5.0.
2. Set up and configure the Ant software.
   • Download and install the Ant software.
   • Set your execution path so that it contains the ant command. For example: ANT-dist-path/bin/ant
3. Make jcov/build the current directory.
4. Edit the jcov/build/build.propertiesfile.
   • The jdk5.home property specifies where the JDK 5.0 is located.
5. Execute the ant command.

The output of the build (jcov-<VERSION>-build directory) contains the following files and subdirectories:

• jcov-<VERSION>.zip -- JCov distribution file. Contains examples, javadocs, jcov.jar and basic documentation files.
• release/ -- Unpacked JCov distribution.
• temp/ -- Temporary build directory.

Additional Build Targets

The following additional targets are available. You might wish to identify these targets to your IDE (for example, NetBeans).