Download

Final releases

Distribution zip

The OptaPlanner distribution zip includes binaries, documentation, examples and sources.

Download OptaPlanner Engine 8.25.0.Final
- Release notes 8 - Upgrade recipe to 8
- License: Apache License 2.0 - Date: Tue 26 July 2022
- Download size: Large (over 90% is due to examples, data sets and documentation)
For Red Hat subscription releases go to the product download site.

Maven

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.25.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.25.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>

Gradle

With Gradle, just add the optaplanner-core dependency in your build.gradle to get started:

dependencies {
  implementation 'org.optaplanner:optaplanner-core:8.25.0.Final'
}

Download OptaWeb Vehicle Routing 8.25.0.Final
- License: Apache License 2.0 - Date: Tue 26 July 2022
For Red Hat subscription releases go to the product download site.

Non-Final releases

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.

Alphas, Betas and CRs

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.