What is the mapping between BRMS / BPM Suite product and maven library version?

Solution Verified - Updated -

Environment

  • Red Hat JBoss BRMS
    • 6.2
    • 6.3
    • 6.4
  • Red Hat JBoss BPM Suite
    • 6.2
    • 6.3
    • 6.4

Issue

We are using 6.4.0.Final-redhat-3 version for our drools dependencies. Does this mean we are using BRMS 6.4.0 ?

Resolution

It's always recommended to use BOM to manage dependencies, as it simplifies the dependency management quite a bit. Here is an example:

<dependencyManagement>
 <dependencies>
  <dependency>
   <groupId>org.jboss.bom.brms</groupId>
   <artifactId>jboss-brms-bpmsuite-platform-bom</artifactId>
   <version>6.4.12.GA-redhat-2</version> <!-- this is correct BOM version for BPM Suite 6.4.12)
   <type>pom</type>
   <scope>import</scope>
  </dependency>
 </dependencies>
</dependencyManagement>

If BOM is used, then adding a dependency looks like this:

<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-compiler</artifactId> 
<!-- it is not necessary to explicitly specify version, because you are using BOM, which is taking care of that -->
</dependency>

If, for any reason, you don't want to or can't use the BOM, then you need to specify the maven version explicitly. Please see the table below, which includes mapping between product version - bom version - and maven library version.

Product Version BOM Version Maven Library Version
BxMS 6.4.12 6.4.12.GA-redhat-2 6.5.0.Final-redhat-27
BxMS 6.4.11 6.4.11.GA-redhat-2 6.5.0.Final-redhat-25
BxMS 6.4.10 6.4.10.GA-redhat-2 6.5.0.Final-redhat-23
BxMS 6.4.9 6.4.9.GA-redhat-2 6.5.0.Final-redhat-21
BxMS 6.4.8 6.4.8.GA-redhat-2 6.5.0.Final-redhat-19
BxMS 6.4.7 6.4.7.GA-redhat-1 6.5.0.Final-redhat-17
BxMS 6.4.6 6.4.6.GA-redhat-1 6.5.0.Final-redhat-16
BxMS 6.4.5 6.4.5.GA-redhat-3 6.5.0.Final-redhat-15
BxMS 6.4.4 6.4.4.GA-redhat-3 6.5.0.Final-redhat-12
BxMS 6.4.3 6.4.3.GA-redhat-2 6.5.0.Final-redhat-9
BxMS 6.4.2 6.4.2.GA-redhat-2 6.5.0.Final-redhat-7
BxMS 6.4.1 6.4.1.GA-redhat-3 6.5.0.Final-redhat-5
BxMS 6.4.0 6.4.0.GA-redhat-2 6.5.0.Final-redhat-2
BxMS 6.3.4 6.3.4.GA-redhat-3 6.4.0.Final-redhat-13
BxMS 6.3.3 6.3.3.GA-redhat-2 6.4.0.Final-redhat-10
BxMS 6.3.2 6.3.2.GA-redhat-2 6.4.0.Final-redhat-8
BxMS 6.3.1 6.3.1.GA-redhat-2 6.4.0.Final-redhat-6
BxMS 6.3.0 6.3.0.GA-redhat-3 6.4.0.Final-redhat-3
BxMS 6.2.3 6.2.3.GA-redhat-3 6.3.0.Final-redhat-12
BxMS 6.2.2 6.2.2.GA-redhat-2 6.3.0.Final-redhat-9
BxMS 6.2.1 6.2.1.GA-redhat-2 6.3.0.Final-redhat-7
BxMS 6.2.0 6.2.0.GA-redhat-1 6.3.0.Final-redhat-5
BxMS 6.1.5 6.1.5.GA-redhat-1 6.2.0.Final-redhat-14
BxMS 6.1.4 6.1.4.GA-redhat-2 6.2.0.Final-redhat-13
BxMS 6.1.3 6.1.3.GA-redhat-2 6.2.0.Final-redhat-11
BxMS 6.1.2 6.1.2.GA-redhat-3 6.2.0.Final-redhat-9
BxMS 6.1.1 6.1.1.GA-redhat-2 6.2.0.Final-redhat-6
BxMS 6.1.0 6.1.0.GA-redhat-2 6.2.0.Final-redhat-4

Note: Similar information is available for Red Hat Decision Manager (RHDM) 7 and for Red Hat Process Automation Manager (RHPAM) 7.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments