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.
Description of problem:
Trying to install Maven using `dnf install maven maven-openjdk17` on a host that previously had only installed java-17-openjdk-devel, so doesn't have java-11-* nor java-1.8.0-* causes additional installation of java-11-openjdk-headles as a dependency of maven-lib package.
Version-Release number of selected component (if applicable):
maven - 3.6.3-14.el9
How reproducible:
Each time
Steps to Reproduce:
1. Get clean minimal RHEL 9.0 installation
2. Install OpenJDK 17 - dnf install java-17-openjdk-devel
3. Install Maven - dnf install maven maven-openjdk17
Actual results:
dnf installs additionally java-11-openjdk-headless
Expected results:
java-17-openjdk-headless is a sufficient dependency for maven
Additional info:
Confirmed. Thank you for the report.
Reproducer:
# podman run -it registry.access.redhat.com/ubi9
# dnf -y install maven-openjdk17
# rpm -e java-11-openjdk-headless
(java-headless or java-11-headless) is needed by (installed) plexus-utils-3.3.0-9.el9.noarch
...
Scope of the change:
- update javapackages-generators to generate requires on (java-headless or java-11-headless or java-17-headless)
- rebuild maven and its runtime dependencies to have new requires generated
Automated regression tests need to be implemented for all JDK versions - 8, 11, 17.