Build-system major drift
Gradle 9 missing project directory included project settings evaluation fail must exist projectDir
A conditionally included subproject causes settings evaluation to fail on an otherwise valid checkout.
Agent Quick Fix
Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.
Product: Gradle 9
Current-contract area: Missing project directory is no longer tolerated
Likely root cause: A conditionally included subproject causes settings evaluation to fail on an otherwise valid checkout.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.Symptom
A conditionally included subproject causes settings evaluation to fail on an otherwise valid checkout.
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 missing project directory included project settings evaluation fail must exist projectDir
site:docs.gradle.org Gradle 9 upgrading missing project directory project directory must exist include
Gradle 9 project directory must exist include settings
Gradle upgrade guide missing project directory must exist writable
https://docs.gradle.org/current/userguide/upgrading_version_8.html
'missing' in https://docs.gradle.org/current/userguide/upgrading_major_version_9.html