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.
Bug 2162308 - maven:3.6 should not pull in more than one Java version
Summary: maven:3.6 should not pull in more than one Java version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: maven
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: pre-dev-freeze
: 8.8
Assignee: Mikolaj Izdebski
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On: 1991521
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-19 10:07 UTC by Jonathan Dowland
Modified: 2023-05-16 10:10 UTC (History)
5 users (show)

Fixed In Version: maven-3.6-8080020230202141236.9d367344
Doc Type: Enhancement
Doc Text:
Clone Of: 1991521
Environment:
Last Closed: 2023-05-16 08:42:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-145746 0 None None None 2023-01-19 10:09:43 UTC
Red Hat Product Errata RHBA-2023:2899 0 None None None 2023-05-16 08:42:12 UTC

Description Jonathan Dowland 2023-01-19 10:07:16 UTC
+++ This bug was initially created as a clone of Bug #1991521 +++

Description of problem:

The point of the maven-openjdk17 metapackage is to permit Maven to be installed and have its dependencies satisfied by OpenJDK 17. See the cloned bug for initial work on that.

The maven-libs package depends on java-headless | java-11-headless. Neither are provided by OpenJDK 17 (see 2080229 for discussion on that), and so maven-libs forces the installation of OpenJDK 8 or 11.

A fix would be to adjust the maven-libs dependency to be

  dependency: (java-headless or java-11-headless or java-17-headless)

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

1:3.6.2-7.module+el8.6.0+13337+afcb49ec.noarch

How reproducible:

Always

Steps to Reproduce:
1. microdnf install maven-openjdk17
2. rpm -qa java-*

Actual results:

java-11-openjdk-...
java-11-openjdk-headless-...
java-17-openjdk-...
java-17-openjdk-headless-...

Expected results:

java-17-openjdk-...
java-17-openjdk-headless-...

Additional info:

It'd be great to finally be able to install maven with any of the redhat-provided OpenJDK versions without pulling in a spare JDK as well. This is a major pain for the containers.

Comment 4 Marián Konček 2023-02-03 10:31:15 UTC
Pre-verification:
Change was commited to dist-git of javapackages-tools. Maven module was rebuilt.
Latest rpm of maven-lib has updated Requires fields.
Tests (/Sanity/openjdk-packages) were added and check for absence of java packages of different versions.
Tests passed.

Comment 9 errata-xmlrpc 2023-05-16 08:42:08 UTC
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


Note You need to log in before you can comment on or make changes to this bug.