<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-core</artifactId>
<version>9.44.0.Final</version>
</dependency>
The OptaPlanner distribution zip includes binaries, documentation, examples and sources.
Download OptaPlanner Engine 9.44.0.Final
License: Apache License 2.0 - Date: Wed 6 September 2023
Download size: Large (over 90% is due to examples, data sets and documentation)
For Red Hat subscription releases go to the product download site.
The OptaPlanner jars are also available in the central maven repository (and also in the JBoss maven repository).
With Maven, just add the optaplanner-core
dependency in your pom.xml
to get started:
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-core</artifactId>
<version>9.44.0.Final</version>
</dependency>
Or better yet, import the optaplanner-bom
to avoid duplicating version numbers
when adding other optaplanner dependencies later on:
<project>
...
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-bom</artifactId>
<type>pom</type>
<version>9.44.0.Final</version>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-core</artifactId>
</dependency>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-test</artifactId>
<scope>test</scope>
</dependency>
...
</dependencies>
</project>
With Gradle, just add the optaplanner-core
dependency in your build.gradle
to get started:
dependencies {
implementation 'org.optaplanner:optaplanner-core:9.44.0.Final'
}
Both OptaPlanner 8 and 9 are equal feature-wise and their APIs have not changed. While OptaPlanner 9 brings compatibility with Jakarta EE 10, Quarkus 3 and Spring Boot 3, OptaPlanner 8 provides full backward compatibility for users who cannot migrate yet. OptaPlanner 8 will keep being released in parallel to OptaPlanner 9 until further notice.
If you are not sure which version to pick, see the following diagram:
To summarize what the diagram shows:
The OptaPlanner distribution zip includes binaries, documentation, examples and sources.
Download OptaPlanner Engine 8.44.0.Final
License: Apache License 2.0 - Date: Wed 6 September 2023
Download size: Large (over 90% is due to examples, data sets and documentation)
For Red Hat subscription releases go to the product download site.
The OptaPlanner jars are also available in the central maven repository (and also in the JBoss maven repository).
With Maven, just add the optaplanner-core
dependency in your pom.xml
to get started:
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-core</artifactId>
<version>8.44.0.Final</version>
</dependency>
Or better yet, import the optaplanner-bom
to avoid duplicating version numbers
when adding other optaplanner dependencies later on:
<project>
...
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-bom</artifactId>
<type>pom</type>
<version>8.44.0.Final</version>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-core</artifactId>
</dependency>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-test</artifactId>
<scope>test</scope>
</dependency>
...
</dependencies>
</project>
With Gradle, just add the optaplanner-core
dependency in your build.gradle
to get started:
dependencies {
implementation 'org.optaplanner:optaplanner-core:8.44.0.Final'
}
Non-Final releases are the best way to test drive new features and APIs to provide feedback before we lock down the API with a Final release. We welcome such feedback in our forum.
An Alpha can be unstable. A Beta should work (it passes automated testing), but its new APIs might still change in the next release. A CR should be almost identical to the Final release.
There is no Alpha or Beta yet because we just released a Final version.
Nightly snapshots are unstable binaries, built automatically by our CI server.
For older community releases, check the release archive.