Timefold Solver Community Edition 1.7.0
In this release of Timefold Solver, we focused mostly on bugfixes, improvements to documentation and to the quickstarts. The release also brings the usual assortment of small tweaks and dependency upgrades.
Featured update: We've made it possible to inject more than one SolverManager in your Quarkus and Spring Boot applications, a feature often requested by the community.
Changelog
🚀 Features
- Support multiple SolverManager instances in Spring Boot (#564, #590)
🐛 Fixes
- Recommended Fit API needs to ignore any unassigned entities/values (#618), closes #581 #618
- Nearby selection pinning support (#614), closes #614
- Pass all subclasses of Throwable to the exception handler in SolverManager
- Ensuring the spent termination property is read in the Quarkus environment (#600), closes #600
- Avoid eager initialization of the Benchmark resources
📝 Documentation
- Adding VRP quickstart documentation (#623), closes #623
- Clearly mention that the timegrain pattern doesn't scale (#611), closes #611
- Add MoveIteratorFactory example to the docs (#606), closes #606
Contributors
We'd like to thank the following people for their contributions:
Timefold Solver Community Edition is an open source project, and you are more than welcome to contribute as well! For more, see Contributing.
Should your business need to scale to truly massive data sets or require enterprise-grade support, check out Timefold Solver Enterprise Edition.
How to use Timefold Solver
To see Timefold Solver in action, check out the quickstarts.
With Maven or Gradle, add the ai.timefold.solver : timefold-solver-core : 1.7.0 dependency in your pom.xml to get started.
You can also import the Timefold Solver Bom (ai.timefold.solver : timefold-solver-bom : 1.7.0)
to avoid duplicating version numbers when adding other Timefold Solver dependencies later on.
Additional notes
The changelog and the list of contributors above are automatically generated. It excludes contributions to certain areas of the repository, such as CI and build automation. This is done for the sake of brevity and to make the user-facing changes stand out more.
