JBoss EAP BOMs: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
=Relationship between BOM and EAP Version= | =Relationship between BOM and EAP Version= | ||
The | The EAP version is specified directly in the BOM declaration: | ||
<syntaxhighlight lang='xml'> | |||
<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> | |||
</syntaxhighlight > | |||
Revision as of 19:23, 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.
Relationship between BOM and EAP Version
The EAP version is specified directly in the BOM declaration:
<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>