Build-system major drift
Gradle 9 assemble no longer builds custom implicit artifact expected ZIP absent release packaging succeeds
Release packaging succeeds locally on the old wrapper but the expected ZIP/JAR is absent on the new wrapper.
Agent Quick Fix
Repair against the current Gradle 9 contract, then keep the change narrow and source-backed.
Product: Gradle 9
Current-contract area: `assemble` no longer builds a custom implicit artifact
Likely root cause: Release packaging succeeds locally on the old wrapper but the expected ZIP/JAR is absent on the new wrapper.
Repair direction: Verifier checks explicit modern configuration and supported daemon/toolchain separation.Symptom
Release packaging succeeds locally on the old wrapper but the expected ZIP/JAR is absent on the new wrapper.
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 assemble no longer builds custom implicit artifact expected ZIP absent release packaging succeeds
site:docs.gradle.org Gradle 9 upgrade guide assemble artifact archives configuration
Gradle upgrade guide 9.0 assemble no longer depends on artifact-producing tasks
"assemble" "implicit artifact" Gradle
Gradle 9.0 upgrading_version_8 archives configuration assemble task
https://docs.gradle.org/current/userguide/upgrading_version_8.html
'archives' in https://docs.gradle.org/current/userguide/upgrading_major_version_9.html