Hey everyone,

We just published version v1.8.0 of JPersist , an open-source ecosystem of highly optimized, Configuration Cache-compliant Gradle plugins designed to automate enterprise Jakarta Persistence (JPA) configurations.

In this release, we didn't just add features (like full Apache OpenJPA toolset orchestration) — we deep-dived into advanced Gradle task engineering to fix common continuous integration pain points.

The Problem: Aggressive Compiler Erasures & CI Pipeline Crashes

When writing custom incremental tasks that process bytecodes, pointing your task @InputDirectory to the compiler's output directory ( build/classes/java/main ) creates an incremental bottleneck. Why?…