JBoss EAP BOMs

Internal

• JBoss Maven Repositories
• Maven Dependencies - BOMs

Overview

The specification of one more more supported JBoss dependencies in a build does not guarantee that all transitive dependencies of the build are resolved to supported dependencies. This is the reason behind using JBoss-curated BOM (bills of materials). These BOMs insure that Maven will prioritize supported JBoss artifacts for all direct and transitive dependencies in the build.

JBoss EAP BOMs are used like any other BOMs:

Using a BOM

Repository

The BOMs are available in the RedHat General Availability Maven Repository.

BOMs

EAP 6

• org.jboss.bom eap6-supported-artifacts https://maven.repository.redhat.com/ga/org/jboss/bom/eap6-supported-artifacts/6.4.15.GA/eap6-supported-artifacts-6.4.15.GA.pom
• jboss-javaee-6.0-with-logging https://maven.repository.redhat.com/ga/org/jboss/bom/eap/jboss-javaee-6.0-with-logging/6.4.15.GA/jboss-javaee-6.0-with-logging-6.4.15.GA.pom
• jboss-javaee-6.0: it contains the Java EE Specification API JARs used by JBoss EAP. This BOM is versioned based ...?

EAP 6 BOM Usage Example

https://github.com/NovaOrdis/playground/tree/master/jboss/bom/eap6

Relationship between BOM and EAP Version

The EAP version is specified directly in the BOM declaration. For EAP 6:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.jboss.bom</groupId>
      <artifactId>eap6-supported-artifacts</artifactId>
      <version>6.4.15.GA</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>