In 2013, as of version
6.0.0.Beta1, Drools Planner was renamed to OptaPlanner.
OptaPlanner is the new name for Drools Planner. OptaPlanner is now standalone, but can still be optionally combined with the Drools rule engine for a powerful declarative approach to planning optimization.
OptaPlanner has graduated from the Drools project to become a top-level JBoss Community project.
OptaPlanner is not a fork of Drools Planner. We simply renamed it.
OptaPlanner (the planning engine) joins its siblings Drools (the rule engine) and jBPM (the workflow engine) in the KIE group.
Our commitment to Drools hasn’t changed.
The efficient Drools rule engine is still the recommended way to do score calculation.
Alternative score calculation options, such as pure Java calculation (no Drools), also remain fully supported.
From a business point of view, there’s little or no change:
The mission remains unchanged:
We’re still 100% committed to put business resource optimization in the hands of everyday Java developers.
The license remains unchanged:
OptaPlanner still has the same open source license, Apache License 2.0.
The release lifecycle remains unchanged:
OptaPlanner is still released at the same time as Drools and jBPM.
Red Hat is considering support subscription offerings for OptaPlanner as part of its BRMS and BPM platforms.
A Tech Preview of OptaPlanner is targeted for BRMS 6.0.
The website has changed to https://www.optaplanner.org.
The distributions artifacts have changed name:
Jar names changes:
drools-planner-core-*.jar is now
drools-planner-benchmark-*.jar is now
Maven identification groupId’s and artifactId’s changes:
org.drools.planner is now
drools-planner-core is now
drools-planner-benchmark is now
As usual, for more information see the Upgrade Recipe in the download zip.
The API’s namespace has changed.
As usual, see the upgrade recipe on how to deal with this efficiently.
Starting from 6.1.0.Final, OptaPlanner will have a 100% backwards compatible API.
OptaPlanner gets its own IRC channels on Freenode: