Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #2096431
I am copying this bug because:
We discovered that this bug is also present in the maven:3.6 stream in RHEL 8.
(But present neither in maven:3.5 nor in maven:3.8)
Description of problem:
JAVA_HOME is not honoured, hard-coded jdk is used instead, thus killing 100% multi-jdk development and purpose of several possible javas in system.
Version-Release number of selected component (if applicable):
maven-3.6.3-14.el9.noarch
Steps to Reproduce:
1. dnf install maven
- that pulls jdk11 in
2. remove all jdks
3. extract custom jdk
4 export correctly JAVA_HOME to point to correct custom JDK
5 try to run maven
Actual results:
/usr/bin/mvn --version
The JAVA_HOME environment variable is not defined correctly
This environment variable is needed to run this program
NB: JAVA_HOME should point to a JDK not a JRE
or:
Steps to Reproduce:
1. dnf install maven
- that pulls jdk11 in
3. extract custom jdk
4 export correctly JAVA_HOME to point to correct custom JDK
5 try to run maven
Actual results:
/usr/bin/mvn --version
Will now work, but will use bad JDK - hardcoded instead of appointed one
Expected results:
Maven will use specified JDK without questioning uses actions, as promised in https://fedoraproject.org/wiki/Changes/Decouple_system_java_setting_from_java_command_setting
Additional info:
This popups form time to time in fedora, but usually gets quickly fixed. I'm wondering why and how it bubbled to rhel
Pre-verified build maven-3.6-8080020230202141236.9d367344
This bug is covered by /Regression/java-home-override test that checks
whether Maven allows overriding JAVA_HOME by calling user:
https://src.fedoraproject.org/tests/maven/blob/main/f/Regression/java-home-override
This test was executed as part of baseos-ci.redhat-module.other.functional
All gating tests passed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (maven:3.6 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2899