A number of additions and updates have been performed on the available Hibernate runtime providers.

When a new Quarkus project/module is to be generated, it is now possible to select the Quarkus stream (see this article) on which the generated application will be based on.

By default, the recommended (latest release) will be selected but you can choose another one:

When you want to define a fallback method thanks to the @Fallback annotation from MicroProfile Fault Tolerance, the code completion is activated on the fallbackMethod member and will propose you available target methods.

When you define a Quarkus launch/debug configuration, it is linked to a specific project from your workspace. If this project has a dependency on another project from the workspace, it will be resolved against the workspace and you don’t have to install the dependency in the local Maven/Gradle cache so that it can be resolved.