Quarkus 3.10.0 now requires a GraalVM installation for quarkusDev when quarkus.native.enabled is set to true

[ThoSap]

Describe the bug

When upgrading Quarkus from a previous version to Quarkus 3.10.0, the Quarkus CLI migrates
quarkus.package.type=native
to

quarkus.package.jar.enabled=false
quarkus.native.enabled=true

With this change, the dev server ./gradleq quarkusDev can no longer start if any other OpenJDK distribution instead of GraalVM is installed.

With previous versions this worked, as for local development for example Eclipse Adoptium is sufficient and building and testing in native mode is only done by the CI pipeline.

Expected behavior

The local dev server ./gradleq quarkusDev should work if the following properties are set without GraalVM installed.

quarkus.package.jar.enabled=false
quarkus.native.enabled=true

Actual behavior

How to Reproduce?

No response

Output of uname -a or ver

Microsoft Windows [Version 10.0.22631.3447]

Output of java -version

OpenJDK 64-Bit Server VM Temurin-21.0.3+9 (build 21.0.3+9-LTS, mixed mode, sharing)

Quarkus version or git rev

3.10.0

Build tool (ie. output of mvnw --version or gradlew --version)

Gradle 8.7

Additional information

implementation 'io.quarkus:quarkus-agroal'
implementation 'io.quarkus:quarkus-arc'
implementation 'io.quarkus:quarkus-awt'
implementation 'io.quarkus:quarkus-cache'
implementation 'io.quarkus:quarkus-config-yaml'
implementation 'io.quarkus:quarkus-jdbc-oracle'
implementation 'io.quarkus:quarkus-jdbc-postgresql'
implementation 'io.quarkus:quarkus-kubernetes'
implementation 'io.quarkus:quarkus-micrometer'
implementation 'io.quarkus:quarkus-micrometer-registry-prometheus'
implementation 'io.quarkus:quarkus-oidc'
implementation 'io.quarkus:quarkus-rest'
implementation 'io.quarkus:quarkus-rest-jackson'
implementation 'io.quarkus:quarkus-scheduler'
implementation 'io.quarkus:quarkus-smallrye-health'
implementation 'io.quarkus:quarkus-smallrye-openapi'

[quarkus-bot]

/cc @geoand (kubernetes), @iocanel (kubernetes), @zakkak (native-image)

[dmlloyd]

I think this was indirectly caused by #39295. On reaugment, the dev mode processor forces the JAR type to be mutable-jar. Previously, this overrode the native-build setting, but now that native has its own flag, this no longer happens. It's a simple fix though.

The interim workaround would be to set quarkus.native.enabled=false while working in dev mode.