Why does quarkusDev depend on testClasses in Gradle?

[rodcheater]

I often find myself in a situation where my tests are not in a buildable state but I need to be able to run the application. However, you can’t run quarkusDev when the tests don’t build:

./gradlew quarkusDev -m

:processResources SKIPPED
:quarkusGenerateAppModel SKIPPED
:quarkusGenerateCode SKIPPED
:quarkusGenerateDevAppModel SKIPPED
:quarkusGenerateCodeDev SKIPPED
:compileJava SKIPPED
:classes SKIPPED
:processTestResources SKIPPED
:compileQuarkusTestGeneratedSourcesJava SKIPPED
:quarkusGenerateTestAppModel SKIPPED
:quarkusGenerateCodeTests SKIPPED
:compileTestJava SKIPPED
:testClasses SKIPPED
:quarkusDev SKIPPED

BUILD SUCCESSFUL in 576ms

Is this a deliberate design decision, or a bug?

Note the quarkusRun does not depend on building the tests:

./gradlew quarkusRun -m

:processResources SKIPPED
:quarkusGenerateAppModel SKIPPED
:quarkusGenerateCode SKIPPED
:quarkusGenerateDevAppModel SKIPPED
:quarkusGenerateCodeDev SKIPPED
:compileJava SKIPPED
:classes SKIPPED
:jar SKIPPED
:quarkusBuildAppModel SKIPPED
:quarkusAppPartsBuild SKIPPED
:quarkusDependenciesBuild SKIPPED
:quarkusBuild SKIPPED
:quarkusRun SKIPPED

BUILD SUCCESSFUL in 507ms

[rodcheater]

Ah, it only happens with Kotlin tests. I think this is just a regression of #20729. I’ll raise a bug.

[rodcheater]

#47495