Open Malandril opened 1 day ago
Since quarkus 3.16.1 the buildForkOptions in the quarkus extensions is no longer used when running quarkus tasks such as quarkusBuild, or imagePush
buildForkOptions
quarkusBuild
imagePush
The buildForkOptions should be used to configure the build tasks, and its actions should be applied to QuarkusBuildTask.
QuarkusBuildTask
The buildForkOptions is not used, and the configuration actions are not executed
quarkus create app quarkus-bug-jib-proxy --gradle-kotlin-dsl --extension='rest'
build.gradle.kts
quarkus { buildForkOptions { println("Build fork options") } }
The line is never printed
uname -a
ver
No response
java -version
3.16.2
mvnw --version
gradlew --version
Gradle 8.10.2
The codeGenForkOptions is still correctly used.
codeGenForkOptions
/cc @geoand (jib,kotlin), @glefloch, @quarkusio/devtools
cc @aloubyansky
The QuarkusBuildTask is incorrectly using the CodeGenForkOptions. A fix was created in #44493.
Describe the bug
Since quarkus 3.16.1 the
buildForkOptions
in the quarkus extensions is no longer used when running quarkus tasks such asquarkusBuild
, orimagePush
Expected behavior
The
buildForkOptions
should be used to configure the build tasks, and its actions should be applied toQuarkusBuildTask
.Actual behavior
The
buildForkOptions
is not used, and the configuration actions are not executedHow to Reproduce?
quarkus create app quarkus-bug-jib-proxy --gradle-kotlin-dsl --extension='rest'
build.gradle.kts
:The line is never printed
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
3.16.2
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 8.10.2
Additional information
The
codeGenForkOptions
is still correctly used.