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.

Description of problem:

/usr/bin/mvn calls "which" if JAVA_HOME is not defined in the environment when it is invoked. However, the RPM does not depend upon the "which" RPM, so "which" may not be installed.


Version-Release number of selected component (if applicable):

3.6.2-6.module+el8.4.0+9250+1786af37

How reproducible:


Steps to Reproduce:
1. unset JAVA_HOME
2. mvn
3.

Actual results:

$ mvn
/usr/bin/mvn: line 98: which: command not found
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

Expected results:

$ mvn
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.052 s
[INFO] Finished at: 2021-09-27T10:56:36Z
[INFO] ------------------------------------------------------------------------
...


Additional info:

This has been witnessed downstream of the ubi8/openjdk-11 container image, which installs maven, but not which:
https://github.com/quarkusio/quarkus-buildpacks/issues/13

Upstream fix: https://github.com/apache/maven/pull/556

Pre-verification:
Change which adds Requires has been added to dist-git.
Newly built maven Requires `which`.
https://brewweb.engineering.redhat.com/brew/rpminfo?rpmID=11905949

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