Скачать или смотреть How to Ensure Your RPM Package Automatically Uses the Correct Java Version on RHEL 8

Learn how to create a self-contained RPM package that automatically selects the right Java version for your application on RHEL 8, eliminating manual setup for your users.
---
This video is based on the question https://stackoverflow.com/q/63469206/ asked by the user 'Illidan' ( https://stackoverflow.com/u/861018/ ) and on the answer https://stackoverflow.com/a/63469747/ provided by the user 'Stephen C' ( https://stackoverflow.com/u/139985/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: RedHat - how RPM may automatically select correct JVM version?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Ensure Your RPM Package Automatically Uses the Correct Java Version on RHEL 8

Distributing your own RPM package can be a daunting task, especially when it comes to making sure all dependencies, including the correct Java version, are installed and configured properly. Let’s explore how to tackle a common issue faced by developers: ensuring that your Java application runs on the correct version of Java without user intervention.

The Problem: Java Version Conflict

Imagine you've packaged your Java application in RPM format targeting Red Hat Enterprise Linux (RHEL) 8. It contains a JAR file that requires Java 11 to run properly, but by default, RHEL 8 comes pre-installed with Java 8. You added a dependency on Java 11 in your RPM spec file, which ensures that Java 11 is installed with your package. However, when your users try to run your application using:

[[See Video to Reveal this Text or Code Snippet]]

They find that the system defaults to Java 8, causing the application to fail. Your goal is to create a seamless experience for your users without requiring additional configuration, such as manually selecting the correct Java version.

Delivering the Solution: A Wrapper Script

To solve this challenge, you need to implement a wrapper script that automatically selects the correct version of Java based on what your application requires.

Step 1: Understanding the Execution Context

When users run a command like:

[[See Video to Reveal this Text or Code Snippet]]

The system uses the version of Java that is currently in the search path, meaning the java command directs to whatever is linked in /usr/bin/java. Consequently, if this link points to Java 8, that’s what will be executed.

Step 2: Creating a Wrapper Script

To ensure your application uses Java 11, you can create a wrapper script with the following considerations:

Determine Java Installation Paths:

Identify where different Java versions are installed by examining the symlinks from /usr/bin/java to the actual executables.

This can be done using commands such as ls -l /usr/bin/java.

Implement Logic in the Wrapper Script:

The script can include logic to check the installed Java versions and select Java 11. Here’s a basic structure of what this could look like:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Packaging with RPM

Integrate the Script into Your RPM:

Include the wrapper script in your RPM package along with your JAR file.

Make sure that the script is executable.

Set the Execution Command:

Instruct users to run your application using the wrapper script rather than invoking Java directly.

Possible Variations

You have a couple of options for enhancing the script:

Installer Choice: Let the installer script determine the Java version and embed it within the generated wrapper script.

User Input: Allow the wrapper script to accept command-line options or environment variables to guide its decision on which Java version to utilize.

Important Considerations

While the /etc/alternatives mechanism is useful, it does not directly address the problem at hand. This approach modifies what java points to system-wide, affecting all applications, not just yours. Dependency management through RPM ensures the required Java version is installed, but does not manage which one gets executed for a specific application.

Conclusion

By implementing a wrapper script, you can make sure your RPM package and the Java application work together seamlessly, without requiring users to manipulate their Java settings. You’ll create a more user-friendly experience and slightly less complexity for your customers. With a bit of additional setup, you can ensure they always run your app