ant_ccase

Using Rational® ClearCase® to audit Jakarta Ant build processes

Applicability

Product

Command type

ClearCase

Data structure

Platform

UNIX®

Linux®

Windows®
Parent topic: Commands for building software (base ClearCase and UCM)
Parent topic: Rational ClearCase command reference

Synopsis

ant -listener CCAudits

Description

Jakarta Ant is an open-source build tool for Java™. Rational ClearCase includes an optional plug-in for Ant, called CCAudits, that enables Rational ClearCase auditing of Ant builds. The auditing process is started by adding the name of a special Java class, CCAudits, as an argument to the Ant command that starts Ant and a listener process. Note that there is no cleartool command associated with auditing Ant build processes.

Prerequisites

To audit Ant builds, Rational ClearCase must be installed on the client host that is running Jakarta Ant and Rational ClearCase services must be started on that client host.

Note: On 64-bit platforms, CCAudits requires a 32-bit Java Development Kit and Java virtual machine.

To enable audits, you must include the file CCAudits.jar in your CLASSPATH either by updating the CLASSPATH environment variable or by copying CCAudits.jar to the lib directory under the ant directory. The default installation directory for CCAudits.jar is /opt/rational/clearcase/java/lib on the UNIX system and Linux, and \Program Files\Rational\ClearCase\bin on Windows.

To enable audits on the UNIX system and Linux, set the appropriate environment variable for your platform, as listed in the following table, to include the Rational ClearCase shlib directory.

Platform Environment variable
Solaris LD_LIBRARY_PATH
Linux LD_LIBRARY_PATH
AIX® LIBPATH
HP-UX SHLIB_PATH

The SHLIB_PATH must also include the usr/lib directory.

By default, the shlib directory is /opt/rational/clearcase/shlib.

The build.xml file

Ant uses the file build.xml to specify the parameters of the build. CCAudits does not require any changes to this file, but it does search the file for optional properties. These optional properties are listed in the following table:

Property Action
CCAudits.debug Prints debugging information to the display device.
CCAudits.ccaudits_dir Specifies a directory under the project directory, which contains the project, subproject, and target derived objects.
CCAudits.auditable_task_list Specifies the list of Ant tasks to be audited. For example:

property CCAudits.auditable_task_list ="javac:jar:javah:war:tar" /

You can either add these optional properties to the file build.xml by using the Ant Property task or you can add them to the file CCAudits.properties and include this properties file by using the Ant Property task. For more information, see the Jakarta Ant documentation.

Limitations

CCAudits has the following limitations:

  • The Rational ClearCase configuration records produced when auditing Ant builds are not used to perform build avoidance. For example, the javac task must determine whether a .class output file is up to date with respect to a corresponding .java source file. In this release, file time stamps are used to make that determination.
  • Parallel tasks in Ant run as sequential tasks.
  • Build times may be longer because of the performance overhead associated with auditing and creating configuration records.
  • On all 64-bit platforms, a Java Development Kit or a Java virtual machine must be running as a 32-bit application for CCAudits to audit Ant build processes successfully.
Feedback