This page represents Fedora guidelines for packaging libraries and applications written in Java and related languages using Java Virtual Machine as bytecode interpreter. It does not aim to extensively describe packaging techniques and tips. RPM macros and commands used here are documented in man pages. Furthermore a separate Java Packaging HOWTO describes Java packaging techniques in detail and includes examples, templates and documentation aimed at packagers and Java developers who are taking their first steps in Java RPM packaging.
Fedora Java packaging is originally based on JPackage Project standards. Over time we have diverged in packaging tools in most areas but we mostly keep backward compatibility with older packages that make use of JPackage standards.
Package naming
Packages MUST follow the standard Fedora package naming guidelines.
Java API documentation MUST be placed into a sub-package called %{name}-javadoc.
Release tags
Packages MUST follow the standard Fedora package versioning guidelines.
Pre-built dependencies
Packages MUST follow the standard Fedora dependency bundling guidelines.
In particular *.class and *.jar files from upstream releases MUST NOT be used during build of Fedora packages and they MUST NOT be included in binary RPM.
JAR file installation
The following applies to all JAR files except JNI-using JAR files and application-specific JAR files (ie. JAR files that can only reasonably be used as part of an application and therefore constitute application-private data).
Split JAR files
If a project offers the choice of packaging it as a single monolithic JAR or several ones, the split packaging SHOULD be preferred.
Installation directory
- All architecture-independent JAR files MUST go into
%{_javadir}or its subdirectory.
- For installation of architecture dependent JAR files, see Packaging JAR files that use JNI.
Filenames
- If the package provides a single JAR file installed filename SHOULD be
%{name}.jar. - If the package provides multiple JAR files, they SHOULD be installed in a
%{name}subdirectory - Versioned JAR files (
*-%{version}.jar) MUST NOT be installed unless the package is a compatibility package - Packages MAY provide alternative filenames as long as they do not conflict with other packages
Here %{name} refers either to package name, or name of subpackage where the jar is installed.
BuildRequires and Requires
Java packages MUST BuildRequire their respective build system:
BuildRequires: maven-localfor packages built with MavenBuildRequires: antfor packages built with antBuildRequires: java-develfor packages built with javac
Java binary packages or their dependencies MUST have Requires (generated by RPM or manual) on:
java-headlessorjava-headless >= 1:minimal_required_versionjavapackages-filesystem
If java-headless requirement is insufficient package MUST have Requires:
javaorjava >= 1:minimal_required_version
Javadoc installation
- javadoc documentation MAY be generated
- If javadoc documentation is generated it MUST be installed into a directory of
%{_javadocdir}/%{name}as part of javadoc subpackage - Directory or symlink
%{_javadocdir}/%{name}-%{version}SHOULD NOT exist. - The javadoc subpackage MUST be declared
noarcheven if main package is architecture specific.
No class-path in MANIFEST.MF
- JAR files MUST NOT include
class-pathentry inside META-INF/MANIFEST.MF
Hardcoded paths
Packages MUST NOT hardcode paths to JAR files they use. When package needs to reference a JAR file, packager SHOULD use one of tools designed to locating JAR files in the system.
Maven pom.xml files
If upstream project is shipping Maven pom.xml files, these MUST be installed. Additionally package MUST install mapping between upstream artifact and filesystem by using the %mvn_install macro.
Additional artifact installation documentation is available forAnt projects and Maven projects.
If upstream project does not ship Maven pom.xml file, official maven repository should be searched and if there are pom.xml files they SHOULD be installed.
If modifications to Maven pom.xml files are needed %pom_* family of macros SHOULD be used
Usage of %pom_* macros is documented in detail in Java Packaging HOWTO.
Wrapper Scripts
Applications wishing to provide a convenient method of execution SHOULD provide a wrapper script in %{_bindir}. Packages SHOULD use %jpackage_script to create these wrapper scripts.
Usage of %jpackage_script macro is documented in Java Packaging HOWTO.
Compatibility packages
In certain cases it might be necessary to create compatibility packages that provide older API/ABI level of the same library. However creating these compatibility packages is strongly discouraged. To standardize and simplify packaging of such compatibility packages following rules apply:
- Compatibility packages MUST be named in the same way as original except addition of version to package name,
- Any JAR and POM files MUST be versioned.
build-classpath and related tools will resolve versioned jar files if versioned jar is asked for. Maven will use dependency information will return versioned jar if it matches the version asked for in the pom file.
Packaging JAR files that use JNI
Applicability
Java programs that wish to make calls into native libraries do so via the Java Native Interface (JNI). A Java package uses JNI if it contains a .so file. Note that this file can be embedded within JAR files themselves.
.png){kind=small}
Note that GCJ packages contain .sos in %{_libdir}/gcj/%{name} but they are not JNI .sos.
Guideline
- JNI packages MUST follow guidelines of ordinary Java packages with exceptions listed here
- JAR files using JNI or containing JNI shared objects themselves MUST be placed in
%{_jnidir}and MAY be symlinked to%{_libdir}/%{name}. - JNI shared objects MUST be placed in
%{_libdir}/%{name}
If the JNI-using code calls
System.loadLibrary you'll have to patch it to use System.load, passing it the full path to the dynamic shared object. You can look at the example.%{_jnidir} expands into %{_prefix}/lib/java, even on 64-bit systems. Java packages using JNI do not support multiarch installation.