Filter
Top Products
Chapter 2 Using the Signature Test Tool 17
Also see “Source and Binary Compatibility Modes” on page 4.
Signature File Contents
Setup generates each signature file with a mandatory header in the first two lines,
followed by the body of the signature file.
Note – Comment lines start with the pound (#) character and can be inserted
anywhere after the first two mandatory header lines.
Signature File Header
Setup generates the first two mandatory header lines of each signature file as
follows:
#Signature file format
#Version version-string
With the following variable replacement values:
■ format is either one of the values described in TABLE 2-3, or empty, that indicates
v0.
■ version-string is a value taken directly from the argument given at the startup
command line to the -apiVersion option (see
TABLE 2-2).
v2.1 This version extends the v2 format to indicate whether an interface is
inherited directly or indirectly. It is read by
SignatureTest
command in SigTest tool 1.3 and later.
v3.1 Generates data for JDK software version 5.0 such as generics,
annotations, and enums.
v4.0 Inherited members are not written to the signature file. Private and
default visibility fields and nested classes that can potentially hide
visible API elements are tracked. In SigTest tool 1.5, all output files
are of this version.
TABLE 2-3 Signature File Format Compatibility (Continued)
Format Description