Build-system major drift
Gradle 9 included project directory not writable generated subproject read-only directory fails Gradle 9
Build setup works on Gradle 8 but fails in a hardened container where an included project directory is not writable.
Agent Quick Fix
Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.
Product: Gradle 9
Current-contract area: Read-only generated subproject directory rejected
Likely root cause: Build setup works on Gradle 8 but fails in a hardened container where an included project directory is not writable.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.Symptom
Build setup works on Gradle 8 but fails in a hardened container where an included project directory is not writable.
Why This Happens
Build scripts can be syntactically plausible while the current build-system major removes implicit artifacts/APIs or raises its daemon runtime floor.
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 included project directory not writable generated subproject read-only directory fails Gradle 9
site:docs.gradle.org Gradle 9 upgrade project directory writable
Gradle 9 upgrade guide writable directory projectDir
Gradle 9 upgrade guide generated project directory
"Project directory" "not writable" Gradle
https://docs.gradle.org/current/userguide/upgrading_major_version_9.html