Runtime support floor
Gradle 9 compatibility Java version daemon requires official documentation
Wrapper starts, then daemon creation fails before any project task executes; compilation target is unrelated.
Agent Quick Fix
The repository may declare a broad engine range while the current tool release silently or explicitly requires a newer patch/minor runtime.
Product: Gradle 9
Current-contract area: Gradle daemon fails on Java 11 while project targets Java 8
Likely root cause: Wrapper starts, then daemon creation fails before any project task executes; compilation target is unrelated.
Repair direction: Verifier accepts either a supported runtime pin or a justified compatible dependency pin, and rejects unsafe monkey patches.Validation Status
Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.
Symptom
Wrapper starts, then daemon creation fails before any project task executes; compilation target is unrelated.
Why This Happens
The repository may declare a broad engine range while the current tool release silently or explicitly requires a newer patch/minor runtime.
Verification
Verifier accepts either a supported runtime pin or a justified compatible dependency pin, and rejects unsafe monkey patches.Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Gradle 9 compatibility Java version daemon requires official documentation
site:docs.gradle.org Gradle 9 compatibility Java 17 Java 11
https://docs.gradle.org/current/userguide/compatibility.html