JBoss EAP BOMs: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 22: Line 22:
=EAP 6=
=EAP 6=


See  
See:


{{External|https://github.com/NovaOrdis/playground/blob/master/jboss/bom/eap6/pom.xml}}
{{External|https://github.com/NovaOrdis/playground/blob/master/jboss/bom/eap6/pom.xml}}


Full example available here:
The full example is available here:


{{External|https://github.com/NovaOrdis/playground/tree/master/jboss/bom/eap6}}
{{External|https://github.com/NovaOrdis/playground/tree/master/jboss/bom/eap6}}

Revision as of 22:08, 6 September 2017

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

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 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



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>


JBoss BOMs Organizatorium

eap6-supported-artifacts

The jboss-javaee-7.0 BOM contains the Java EE Specification API JARs used by JBoss EAP.

To use this BOM in a project, add a dependency for the GAV that contains the version of the JSP and Servlet API JARs needed to build and deploy the application.

The following example uses the 1.0.3.Final-redhat-1 version of the jboss-javaee-7.0 BOM.

<dependencyManagement>
 <dependencies>
   <dependency>
     <groupId>org.jboss.spec</groupId>
     <artifactId>jboss-javaee-7.0</artifactId>
     <version>1.0.3.Final-redhat-1</version>
     <type>pom</type>
     <scope>import</scope>
   </dependency>
   ...
 </dependencies>
</dependencyManagement>
<dependencies>
 <dependency>
   <groupId>org.jboss.spec.javax.servlet</groupId>
   <artifactId>jboss-servlet-api_3.1_spec</artifactId>
   <scope>provided</scope>
 </dependency>
  ...
</dependencies>