Chapter 2. Red Hat Build of OptaPlanner 8.33 new features

Red Hat Build of OptaPlanner is now integrated with the Red Hat build of Quarkus platform. Versions of platform artifact dependencies, including OptaPlanner dependencies, are maintained in the Quarkus bill of materials (BOM) file, com.redhat.quarkus.platform:quarkus-bom. When you use the Quarkus BOM file with your OptaPlanner projects, you do not need to specify which dependency versions work together. Instead, you can import the Quarkus BOM file to the pom.xml configuration file, where the dependency versions are included in the <dependencyManagement> section. Therefore, you do not need to list the versions of individual Quarkus dependencies that are managed by the specified BOM in the pom.xml file.

In most cases, links between planning variables and value ranges are auto-detected. Therefore, the @ValueRangeProvider annotation no longer needs to provide an id property. Likewise, planning variables no longer need to reference value range providers through the valueRangeProviderRefs property.

No code changes or configuration changes are required. If you prefer clarity over brevity, you can continue to explicitly reference your value range providers.

OptaPlanner support for serializing into XML using XStream is deprecated with this release. The optaplanner-persistence-xstream module and all classes that it contains are now deprecated and will be removed in a future release of Red Hat Build of OptaPlanner. To continue serializing into XML, switch to the optaplanner-persistence-jaxb module.

All examples in the optaplanner-examples module have been refactored to JSON by using the optaplanner-persistance-jackson module. Quickstarts are affected by these changes because they were already serializing into JSON.

The following examples were removed from the optaplanner-examples directory: