-
Bug
-
Resolution: Done
-
Major
-
7.2.1.CR2
-
None
-
RHEL7
In case that one would like to install EAP with JDK11 use, there is a new jboss-eap7-jdk11 group defined for such scenario. Although, at the moment, when I perform:
yum groupinstall jboss-eap7-jdk11
then I can see that no eap7-wildfly-java-jdk11 package is installed. Instead, the eap7-wildfly-java-jdk8 with java-1.8.0-openjdk, java-1.8.0-openjdk-headles are grabbed for installation.
Regarding to the groupinfo, I can see:
# yum groupinfo jboss-eap7
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Group: Red Hat JBoss EAP 7.2
Group-Id: jboss-eap7
Description: Red Hat JBoss Enterprise Application Platform 7.2 on JDK 8
Mandatory Packages:
eap7-artemis-native-wildfly
eap7-runtime
eap7-wildfly
+eap7-wildfly-jdk8
eap7-wildfly-modules
# yum groupinfo jboss-eap7-jdk11
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Group: Red Hat JBoss EAP 7.2 on JDK 11
Group-Id: jboss-eap7-jdk11
Description: Red Hat JBoss Enterprise Application Platform 7.2 on JDK 11
Mandatory Packages:
=eap7-artemis-native-wildfly
=eap7-runtime
=eap7-wildfly
-eap7-wildfly-jdk11
=eap7-wildfly-modules
so I am curious whether rootcause isn't in the fact that 'eap7-wildfly-jdk8' and 'eap7-wildfly-jdk11' are used instead of 'eap7-wildfly-java-jdk8' and 'eap7-wildfly-java-jdk11'. This is just a guess, though.
Note that one can use a workaround for default installation to use JDK11 like this:
# yum install java-11-openjdk eap7-wildfly-java-jdk11 # yum remove java-1.8.0-openjdk java-1.8.0-openjdk-headless eap7-wildfly-java-jdk8
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
