Writes test results to the output-dir, which
must already exist. By default, the results files are created in the current
directory.

-rlevel

--reportlevellevel

Sets the output report level to one of the
following values:

a or all - Reports all
results. This is the default in both verbose and non verbose modes.

w or warnings - Reports
only warning and failure results.

f or failures - Reports
only failure results.

-n

--notimestamp

Does not append the timestamp to the output file name.

-?

--help

Displays help for the verifier command. If you use
this option, you do not need to specify an EAR, WAR, RAR, or JAR file.

-V

--version

Displays the verifier tool version. If you use this
option, you do not need to specify an EAR, WAR, RAR, or JAR file.

-u

--gui

Opens a graphical interface for performing verification. If you use
this option, you do not need to specify an EAR, WAR, RAR, or JAR file. For
more information, see the verifier online help.

For example, the following command runs the verifier in
verbose mode and writes all the results of static verification of the ejb.jar file to the output directory ResultsDir:

verifier -v -r a -d ResultsDir ejb.jar

The results files are ejb.jar_verifier.timestamp.txt and ejb.jar_verifier.timestamp.xml. The format of the timestamp is yyyyMMddhhmmss.

If the verifier runs successfully, a result code
of 0 is returned. This does not mean that no verification
errors occurred. A nonzero error code is returned if the verifier fails
to run.

Ant Integration

You can integrate the verifier into an Ant build file as a target and use the Ant call feature to call
the target each time an application or module is assembled. This is because
the main method in com.sun.enterprise.tools.verifier.Verifier is callable from user Ant scripts. The main method
accepts the arguments described in Table 3–4.