Chapter 3. Java project migration

Procedure

1. Open the pom.xml file of the project and remove the <version> tag from any dependencies under the following groups:

   • org.kie
   • org.drools
   • org.jbpm
   • org.optaplanner

2. Add the Red Hat Business Automation bill of materials (BOM) dependency under the <dependencies> tag within the <dependencyManagement> section:

   <dependency>
     <groupId>com.redhat.ba</groupId>
     <artifactId>ba-platform-bom</artifactId>
     <version>7.1.0.GA-redhat-00002</version>
     <scope>import</scope>
     <type>pom</type>
   </dependency>

   Copy to Clipboard

   The Red Hat Business Automation BOM applies to both Red Hat Decision Manager and Red Hat Process Automation Manager. When you add the BOM files, the correct versions of transitive dependencies from the provided Maven repositories are included in the project. The BOM <version> is the version of the com.redhat.ba:ba-platform-bom Red Hat Business Automation artifact in the Maven repository. You can view the version of the artifact by entering the repository and navigating to the maven-repository/com/redhat/bom/ba/ba-platform-bom directory.

3. If your code uses any Drools CDI annotations (@KReleaseId , @KContainer, @KBase, @KSession), also add the following dependency:

   <dependency>
     <groupId>org.drools</groupId>
     <artifactId>drools-cdi</artifactId>
   </dependency>

   Copy to Clipboard

   This dependency is necessary because the CDI extension for processing the annotations is now defined using a separate module. Without this dependency, the annotations do not work.

4. Replace the legacy org.guvnor dependency (if applicable) with the new org.uberfire dependency.

   Legacy org.guvnor dependency:

   <dependency>
     <groupId>org.guvnor</groupId>
     <artifactId>guvnor-rest-client</artifactId>
   </dependency>

   Copy to Clipboard

   New org.uberfire dependency:

   <dependency>
     <groupId>org.uberfire</groupId>
     <artifactId>uberfire-rest-client</artifactId>
   </dependency>

   Copy to Clipboard
5. Update the version of the project artifact and save the pom.xml file.

Procedure

1. Rebuild each Java project using a regular Maven build.

   $ mvn clean install

   Copy to Clipboard

2. Review all project data in each build to confirm successful migration.

   If you encounter build errors, verify that the project dependencies have been updated correctly. To review other product changes that may have impacted your Java project, see Chapter 4, Other migration considerations.