JAVA(1M)MAKE ASSERTION OPERATORS AND RULESJAVA(1M)


NAME

:JAVA: - java assertion operator

SYNOPSIS

:JAVA: [ options ] [ default-pattern ] [ manifest.mf ] [ directory/file-pattern ] [ directory ] [ relative-path-name(.jar|.java) ] [ { manifest } ]

DESCRIPTION

:JAVA: activates all java rule and variable definitions. See JAR(1M) for details on compiling .java source into .class objects.

The options are:

--code

Include .java source code in jars managed by the :JAR: and :WAR: assertion operators.
--compatibility=level

Sets the diagnostic message level for the $(JAVA),$(JAVAC), and $(JAR) command compatibility checks. level may be one of:
< 0
java compatibility diagnostic messages will be listed if -level >= the current debug level. The default debug level is 0.
0
java compatibility diagnostic messages will be listed on the standard error with no command identification prefix. nmake continues execution after each diagnostic and the nmake exit code is not affected.
1
java compatibility diagnostic messages will be listed as warnings. nmake continues execution after each diagnostic and the nmake exit code is not affected.
2
java compatibility diagnostic messages will be listed as errors. nmake continues execution after each diagnostic and the nmake exit code is 1.
>=3
java compatibility diagnostic messages will be listed as errors. nmake exits after the first diagnostic with exit code level-2.

VARIABLES AND ATOMS

JAVA
The java runtime command.
JAVAFLAGS

The java runtime command options.
JAVAC

The java compiler that translates .java files to .class bytecode objects.
JAVACFLAGS

The java compiler options. The -classpath option is automatically generated from the directory and jar file prerequisites of .SOURCE.class .
JMAKE

The java dependency analysis command (formerly named javamake.) This is the java side of the nmake(1) implicit dependency analysis. It is called whenever the input .java files change. jmake calls javac on the smallest subset of .java files that will bring the target up to date, re-computes the dependencies and prerequisites, and saves the java state in a java specific state file.
JMAKEFLAGS

The java dependency analysis command options, mostly used by the java specific rules. See jmake(1) or the output of jmake --man for details.
JAVACLASSES

The root directory where generated .class files are placed. The default is target.classes, where target is the name of the generated jar (or ear or war) archive, java by default.
JAVADIR

The installation directory for generated .class and .jar files. Generated files are installed by the nmake install action. The default is $(INSTALLROOT)/lib/java.
JAVA.SUFFIX.CLASS

The java class file suffix.
JAVA.SUFFIX.CLASSES

The jar temporary class file root directory suffix.
JAVA.SUFFIX.CODE

The jar code file list temporary file suffix.
JAVA.SUFFIX.DATA

The jar data file list temporary file suffix.
JAVA.SUFFIX.JAVA

The java source file suffix.
JAVA.SUFFIX.JAR

The jar file suffix.
JAVA.SUFFIX.MANIFEST

The jar manifest file suffix.
JAVA.SUFFIX.STATE

The jmake state file suffix.
JAVA.SUFFIX.WAR

The war (web jar) file suffix.
JAVA.SUFFIX.UPDATES

The jmake update list file suffix.
JAVA.VERSION.SEPARATOR

The versioned jar files naming convention is base$(JAVA.VERSION.SEPARATOR)version.suffix.

SEE ALSO

JAR(1M), WAR(1M), jmake(1), nmake(1)

IMPLEMENTATION

JAVA.mk (AT&T Research) 2011-07-25


July 28, 2011