-
Bug
-
Resolution: Done
-
Blocker
-
7.3.0.Beta
-
None
Current build of eap7-wildfly package for EAP7.3.0.Beta on RHEL7 requires JDK8 directly. This is wrong as since 7.2.0 we support both JDK8 and JDK11. As such, new eap7-wildfly-java-jdk11 and eap7-wildfly-java-jdk8 metapackages have been introduced since EAP7.2.1 as a fix for JBEAP-16017. These provide eap7-wildfly-java item which has been part of eap7-wildfly package since EAP7.2.1. This does not apply to current EAP7.3.0.Beta release:
# rpm -q --requires eap7-wildfly /bin/sh /bin/sh /bin/sh /bin/sh /bin/sh config(eap7-wildfly) = 0:7.3.0-4.Beta_redhat_00001.1.el7eap eap7-runtime eap7-runtime eap7-wildfly-modules java >= 1:1.8 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 shadow-utils systemd-units systemd-units systemd-units rpmlib(PayloadIsXz) <= 5.2-1
I believe we should ditch the 'java >= 1:1.8' record from there and add 'eap7-wildfly-java' instead.
This discrepancy may not be a big issue if customer installs EAP via yum group command as group definition contains appropriate requirements. Although, I believe we should keep consistent to what we introduced in previous releases.
- is related to
-
JBEAP-16017 EAP7.2 RPMs does not match with provides from java-11-openjdk package
- Closed