JBoss EAP BOMs: Difference between revisions
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
</dependencyManagement> | </dependencyManagement> | ||
</syntaxhighlight > | </syntaxhighlight > | ||
=Available BOMs= | |||
* eap6-supported-artifacts | |||
* jboss-javaee-6.0: it contains the Java EE Specification API JARs used by JBoss EAP. This BOM is versioned based ...? |
Revision as of 19:28, 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.
The JBoss BOMs are included in the JBoss Maven Repository.
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>
Available BOMs
- eap6-supported-artifacts
- jboss-javaee-6.0: it contains the Java EE Specification API JARs used by JBoss EAP. This BOM is versioned based ...?