When using Gradle's new configuration cache feature, the build fails if paperweight-userdev cannot rely on cache and has to produce a bundled jar locally with the following error message:
Configuration cache problems found in this build.
1 problem was found storing the configuration cache.
- Class `io.papermc.paperweight.util.Jar_runnerKt`: external process started '/usr/lib/jvm/java-21-amazon-corretto/bin/java -Dpaperclip.patchonly=true -classpath [...]/module/[...]/dev-bundle/1.20.4-R0.1-SNAPSHOT/paperweight/setupCache/extractDevBundle.dir/data/paperclip-mojang+yarn.jar io.papermc.paperclip.Main'
See https://docs.gradle.org/8.10.2/userguide/configuration_cache.html#config_cache:requirements:external_processes
> Starting an external process '/usr/lib/jvm/java-21-amazon-corretto/bin/java -Dpaperclip.patchonly=true -classpath /usr/lib/jvm/java-21-amazon-corretto/bin/java -Dpaperclip.patchonly=true -classpath [...]/module/[...]/dev-bundle/1.20.4-R0.1-SNAPSHOT/paperweight/setupCache/extractDevBundle.dir/data/paperclip-mojang+yarn.jar io.papermc.paperclip.Main' during configuration time is unsupported.
When using Gradle's new configuration cache feature, the build fails if paperweight-userdev cannot rely on cache and has to produce a bundled jar locally with the following error message: