[7.0] Minecraft Classes not being found on first build (e.g. CI or after clean)

[BlayTheNinth]

Building locally works fine.

On CI, I get compile errors due to missing Minecraft classes.

• Version: Tried both 7.0.0-rc.2 and [7,8), also using jarjar 0.2.3
• build.gradle (subproject in multi-loader build): https://github.com/TwelveIterationMods/Balm/blob/1.21.11/forge/build.gradle - almost identical to the MDK examples linked
• Build Logs: https://github.com/TwelveIterationMods/Balm/actions/runs/20642536050/job/59276175740

I tried to clear caches in GitHub Actions and also tried to explicitly depend on syncMavenizer (one of the workarounds suggested for #1013), although it seems like the syncMavenizer was running fine before too, it's just still the same end result of missing Minecraft classes.

I also noticed another error that seems to be related to eventbus-validator, but even after removing it the above missing classes issue persists.

[PaintNinja]

Regarding the EventBus validator, please retry with the latest version (7.0.0 at the time of writing, no beta) and file an issue on the EventBus repo if the issue persists.

[LexManos]

So, the sync task is running https://github.com/TwelveIterationMods/Balm/actions/runs/20642536050/job/59276175740#step:8:70
Is there any way I can get a log with --dependencies and ideally a buildscan?

[BlayTheNinth]

Turns out I can reproduce it locally too - it looks like the first build after a clean fails, then subsequent ones are fine.

Build Scan (failed, right after clean): https://scans.gradle.com/s/4744xrpxgq3dq
Build Scan (success, right after the failed one): https://scans.gradle.com/s/nwdjq4vyhavhi

This was with ./gradlew :forge:syncMavenizer :forge:dependencies :forge:build --scan '-Pversion=21.11.4-SNAPSHOT' on https://github.com/TwelveIterationMods/Balm 1.21.11 branch

Same issue on the JarJar/fg7 example too:
./gradlew clean
./gradlew syncMavenizer build -> fail
./gradlew syncMavenizer build -> success

Running ./gradlew an extra time before building in my CI for Forge jobs fixes it as a workaround.

[Jonathing]

Lex and I are actively investigating how to work with Gradle in a way that allows the delaying of the compile classpath's resolution. Until then, please run syncMavenizer by itself before running build.