Gradle’s configuration cache significantly reduces build times by reusing the results of project configuration across invocations. Currently, Hibernate Reactive’s local build plugins are not fully compatible with this feature, which prevents contributors from taking advantage of faster feedback loops.

Adjusting the custom/local plugins in the repository to be configuration-cache compliant would bring multiple benefits:

• ⚡ Faster local builds (especially for repeated test cycles).

• ✅ Better developer experience for external contributors.

• 📦 Aligns with Gradle’s modern performance recommendations.

TODO list:

• Check all plugins used and generate a list with status of compatibility with this feature, see Help community Gradle plugins adopt the configuration cache gradle/gradle#13490
• If some plugins are not compatible, isolated it use and document how use that. E.g. ascii doctor plugin is not compatible yet. Resolve Gradle configuration cache issues asciidoctor/asciidoctor-gradle-plugin#730
• Refactor local plugins and custom tasks to being compatible with valid inputs and add test for plugins (opt*).
• Test in local and document suggestions including CI/CD command used (build, runAllExamplesOnX)