Build-system major drift

docs.gradle.org upgrading_version_9 jcenter removed

Settings or build evaluation fails with a missing-method error only after moving to Gradle 9.

Gradle 9JVM build systemsBuild-system major driftgradle9

Agent Quick Fix

Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.

Product: Gradle 9
Current-contract area: `jcenter()` repository method removed
Likely root cause: Settings or build evaluation fails with a missing-method error only after moving to Gradle 9.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.

Symptom

Settings or build evaluation fails with a missing-method error only after moving to Gradle 9.

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.

site:docs.gradle.org Gradle 9 jcenter removed jcenter() repository method
site:docs.gradle.org/current/userguide upgrading_version_9 jcenter
https://docs.gradle.org/current/dsl/org.gradle.api.artifacts.dsl.RepositoryHandler.html
docs.gradle.org upgrading_version_9 jcenter removed
https://docs.gradle.org/current/userguide/upgrading_version_8.html
'jcenter' in https://docs.gradle.org/current/userguide/upgrading_version_8.html
https://docs.gradle.org/current/userguide/upgrading_version_6.html