Explaining the eap-runtime-artifacts vs jboss-eap-javaee8 BOM's separation reason.
Issue
After reading Manage Project Dependencies I am still missing the point: why these two BOM's are divided into two (rather than merged into one).
<dependency>
<groupId>org.jboss.bom</groupId>
<artifactId>eap-runtime-artifacts</artifactId>
<version>7.2.6.GA</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.jboss.bom</groupId>
<artifactId>jboss-eap-javaee8</artifactId>
<version>7.2.6.GA</version>
<type>pom</type>
<scope>import</scope>
</dependency>
I compared libraries among them and they are almost fully distinct (notable exclusion is hibernate-core: both BOM's declare identical version: 5.3.14.Final-redhat-00001
). Can you please provide some explanation for this? My suggestion would be to describe the exact difference between two BOM's i.e. eap-runtime-artifacts
vs. jboss-eap-javaee8
in documentation.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.2.6
- 7.3 Beta
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.