Build plugin/config relocation

Gradle 9 plugin alias version catalog bundle plugins block unresolved reference

A plugin alias expression valid in the previous wrapper becomes an unresolved reference.

Gradle 9JVM build systemsBuild plugin/config relocationgradle9

Agent Quick Fix

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

Product: Gradle 9
Current-contract area: Version-catalog bundle used in `plugins {}` no longer resolves
Likely root cause: A plugin alias expression valid in the previous wrapper becomes an unresolved reference.
Repair direction: Verifier checks the current package identity/config format and a real transformed output.

Symptom

A plugin alias expression valid in the previous wrapper becomes an unresolved reference.

Why This Happens

The old package/config name is syntactically valid, but current tool packaging and discovery rules live in external release documentation.

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 plugin alias version catalog bundle plugins block unresolved reference
site:docs.gradle.org version catalog bundles plugins block alias Gradle 9
Gradle version catalog bundles plugins alias unresolved reference
https://docs.gradle.org/current/userguide/version_catalogs.html
'[bundles]' in https://docs.gradle.org/current/userguide/version_catalogs.html
https://docs.gradle.org/current/userguide/upgrading_version_8.html
https://docs.gradle.org/current/userguide/upgrading_major_version_9.html
'Removal of libraries and bundles from version catalogs in the plugins' in https://docs.gradle.org/current/userguide/upgrading_major_version_9.html