JBoss EAP BOMs

From NovaOrdis Knowledge Base
Jump to: navigation, search

Internal

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. Transitive dependencies will be managed to the correct supported dependency version where applicable. The EAP version can be specified when using a BOM.

JBoss EAP BOMs are used like any other BOMs:

Using a BOM

The JBoss BOMs are being developed here: https://github.com/jboss-developer/jboss-eap-boms. Different branches are maintained for different JBoss EAP versions. Then they are published in the RedHat General Availability Maven Repository.

EAP 7

See:

https://github.com/NovaOrdis/playground/blob/master/jboss/bom/eap7/pom.xml

The full example is available here:

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

More details about EAP 7 and Maven are available here:

https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/development_guide/#use_the_maven_repository

EAP 7 BOMs

EAP 6

See:

https://github.com/NovaOrdis/playground/blob/master/jboss/bom/eap6/pom.xml

The full example is available here:

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

More details about EAP 6 and Maven are available here:

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-Maven_Guide.html

EAP 6 BOMs