Quarkus (Gradle) build should not run tests

Description

While building the application I’ve noticed that ./gradlew build -Dquarkus.package.type=fast-jar will also run all the tests:

[x80486@uplink:~/Workshop/Development/kotlin-quarkus]$ ./gradlew build -Dquarkus.package.type=fast-jar 
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/6.8.2/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build 

> Task :quarkusGenerateCode
preparing quarkus application

> Task :compileKotlin
> Task :compileJava NO-SOURCE
> Task :processResources
> Task :classes
> Task :inspectClassesForKotlinIC
> Task :jar
> Task :startScripts
> Task :distTar
> Task :distZip

> Task :quarkusGenerateCodeTests
preparing quarkus application

> Task :compileTestKotlin
> Task :compileTestJava NO-SOURCE
> Task :processTestResources
> Task :testClasses
> Task :test

> Task :quarkusBuild
building quarkus jar

> Task :assemble
> Task :check
> Task :build

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.8.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 6s
13 actionable tasks: 13 executed

I think this should be avoided because that’s a different (usually time consuming) stage/task that’s triggered on a different phase.

Implementation Ideas

Make the Gradle (and/or Maven) plugin avoid check and/or test, somehow like this command: ./gradlew -Dquarkus.package.type=fast-jar build --exclude-task=check — that simple I guess 😓

[glefloch]

Actually build is a default gradle task. If you only need the quarkus build, you can call the quarkusBuild task which does not depend on test.

[glefloch]

yes, I’m going to update the docs.