This section describes most of directories used for Java packaging. Each directory is named in RPM macro form, which shows how it should be used in RPM spec files. Symbolic name is followed by usual macro expansion (i.e. physical directory location in the file system) and short description.
Directory that holds all JAR files that do not contain or use native code and do not depend on a particular Java standard version. JAR files can either be placed directly in this directory or one of its subdirectories. Often packages create their own subdirectories there, in this case subdirectory name should match package name.
Directory where architecture-specific JAR files are installed. In particular JAR files containing or using native code (Java Native Interface, JNI) should be installed.
Root directory where all Java API documentation (Javadoc) is installed. Each source package usually creates a single subdirectory containing aggregated Javadocs for all binary packages it produces.
Directory where Project Object Model (POM) files used by Apache Maven are installed. Each POM must have name that strictly corresponds to JAR file in
ivy.xmlfiles used by Apache Ivy are installed. Each XML must have name that strictly corresponds to JAR file in
Root directory where different Java Virtual Machines (JVM) are installed. Each JVM creates a subdirectory, possibly with several alternative names implemented with symbolic links. Directories prefixed with
javacontain Java Development Kit (JDK), while directories which names start with
jrehold Java Runtime Environment (JRE).
Directories containing configuration files for Java Virtual Machines (JVM).
Directories containing implementation files of Java Virtual Machines (JVM). Describing them in detail is out of scope for this document. Purpose of each directory is commented briefly in
/etc/rpm. More detailed description can be found in JPackage policy.
Directory containing Java configuration files. In particular it contains main Java configuration file —