Originates in https://issues.redhat.com/browse/ENTSBT-839

Registry used by odo: https://github.com/odo-devfiles/registry/tree/master/devfiles/java-quarkus

from command line:

be able to do ` odo create java-quarkus` in empty directory; there should be two starters to choose from `community` and `redhat-product`; community grabs latest from code.quarkus.io and redhat-product from code.quarkus.redhat.com.

be able to run `odo create java-quarkus` in existing quarkus project.

in both cases result be a project with a devfile.yaml and you can build the project 100% independent from openshift/devfile using normal quarkus mvn commands and also be able to use odo workflows (see https://odo.dev/docs/deploying-a-devfile-using-odo/#deploying-a-quarkus-application-to-a-kubernetes--openshift-cluster).

i.e. after project created with odo you should be able to do:

odo login

odo push

that should deploy app using odo workflow.

odo watch should also work and you should see changes made on disk take effect on the deployment.

Note:at this stage the watch feature are not fully using devmode/remove devmode its using odos own generic publish approach.

Further more upcoming version of openshift will include the devfile so similar workflow should be doable via openshift dev console.
This will be handled in separate RFE once the feature gets available in OpenShift.