This issue is "blocker" because is a regression.

When you create an app with Quarkus-cli 2.6.3, the tool detects the java version that is running in the developer environment and the created app has the same java version as the host. 

This feature is broken in Quarkus 2.7.5.Final

Reproducer: 

Quarkus 2.6.3

jbang app install --name qs2.6.3 io.quarkus:quarkus-cli:2.6.3.Final:runner 

qs2.6.3 create app app

The pom has the same Java version as the host machine. 

Quarkus 2.7.5

jbang app install --name qs2.7.5 io.quarkus:quarkus-cli:2.7.5.Final:runner  

qs2.7.5 create app app

Pom Java version:

<maven.compiler.release>11</maven.compiler.release> 

Expected version: 17

TestDevelopment:
https://github.com/quarkus-qe/quarkus-test-suite/pull/582

cmd: 

mvn clean verify -Dall-modules -Dinclude.quarkus-cli-tests -pl quarkus-cli -Dit.test=QuarkusCliCreateJvmApplicationIT#shouldCreateApplicationOnJvm