Closed miurahr closed 9 months ago
You build parameters when build time.
You should build command parameters when configuration phase.
Most probably won't support config cache due to necessity to run external process to build command line (need jdk version to check parameters compatibility).
Meanwhile marked task as non-compatible in order to enable builds.
Most probably won't support config cache due to necessity to run external process to build command line (need jdk version to check parameters compatibility).
Meanwhile marked task as non-compatible in order to enable builds.
Gradle support execution of external command in a way of non-breaking configuration cache feature and without a crash.
It is ok that jpackage plugin does not support configuration cache, means that it does not reuse configuration, but it should not mean the plugin crash when configuration-cacahe enabled.
The cause is
I think you can replace it with new File()
java standard constructor rather than getProject().file()
.
Gradle recommended to use file()
because Gradle records files in an internal table to track files for gradle configuration cache feature. When the plugin does not support cache feature, Project.file()
is not mandatory.
Crashing issue should be gone in 1.6.0
When configure
jpackage
task with configuratin cache on Gradle 8.4, it failed.it looks happened where
JPackageTask
try to invokejpackage
commandGradle migration guide suggests to use
providers.exec
instead ofProject.exec
Stack trace
error message
configuration
gradle.properties