Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24612

Comps group for EAP8 seems to be incorrect

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 8.0.0.GA-CR1, 8.0.0.GA
    • 8.0.0.Beta
    • RPM
    • None
    • False
    • None
    • False

      It looks like the comps-group.xml file isn't perfectly correct with regards the required package names.

      I can see warnings when I perform following commands:

      # dnf groupinstall jboss-eap8-jdk11
...
No match for group package "java-11 or java-11-headless"

      and

      # dnf groupinstall jboss-eap8
...
No match for group package "java-17 or java-17-headless"

      This causes that for both groups, java-11-openjdk-headless is actually installed only, which is a bug for jboss-eap8 group at least.

      Excerpt from current content of comps-group.xml file:

      <group>
<id>jboss-eap8-jdk11</id>
<default>false</default>
<uservisible>true</uservisible>
<display_order>1024</display_order>
<name>Red Hat JBoss EAP 8 on JDK 11</name>
<description>Red Hat JBoss Enterprise Application Platform 8.0 on JDK 11</description>
<packagelist>
<packagereq type="mandatory">eap8-artemis-native-wildfly</packagereq>
<packagereq type="mandatory">eap8-runtime</packagereq>
<packagereq type="mandatory">eap8-wildfly</packagereq>
<packagereq type="mandatory">eap8-wildfly-modules</packagereq>
<packagereq type="mandatory">java-11 or java-11-headless</packagereq>
</packagelist>
</group>
<group>
<id>jboss-eap8</id>
<default>false</default>
<uservisible>true</uservisible>
<display_order>1024</display_order>
<name>Red Hat JBoss EAP 8 on JDK 17</name>
<description>Red Hat JBoss Enterprise Application Platform 8.0 on JDK 17</description>
<packagelist>
<packagereq type="mandatory">eap8-artemis-native-wildfly</packagereq>
<packagereq type="mandatory">eap8-runtime</packagereq>
<packagereq type="mandatory">eap8-wildfly</packagereq>
<packagereq type="mandatory">eap8-wildfly-modules</packagereq>
<packagereq type="mandatory">java-17 or java-17-headless</packagereq>
</packagelist>

      So problem is that given mandatory java package names aren't correct. I suppose there should be following values:

      <packagereq type="mandatory">java-11-openjdk or java-11-openjdk-headless</packagereq>

      and

      <packagereq type="mandatory">java-17-openjdk or java-17-openjdk-headless</packagereq>

      Not sure where the comps-group.xml file is defined, maybe this is an issue against RCM?

              Unassigned Unassigned
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: