Build-system major drift
Gradle 9 archives configuration removed custom artifacts no matching artifact producer task exists
Publishing or distribution task reports no matching artifact although the producer task still exists.
Agent Quick Fix
Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.
Product: Gradle 9
Current-contract area: Custom artifact no longer appears in `archives` configuration
Likely root cause: Publishing or distribution task reports no matching artifact although the producer task still exists.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.Symptom
Publishing or distribution task reports no matching artifact although the producer task still exists.
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 archives configuration removed custom artifacts no matching artifact producer task exists
site:docs.gradle.org Gradle 9 archives configuration
Gradle archives configuration deprecated
"archives" "configuration" "Gradle 9"
https://docs.gradle.org/current/userguide/upgrading_major_version_9.html