Latest posts

When the new Quarkus project wizard was initially design, there were a few Quarkus extensions so it was not difficult to find one from the total list. Now that the Quarkus ecosystem is growing fast, it was difficult even of the extensions were grouped into categories.

In order to cope with this issue, the extensions and categories are now displayed in a tree (first level is categories, second level is extensions).

This new tree can now be filtered through a text field. If user enter some characters, only extensions matching this filter will be displayed in the tree.

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

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

Qute templates support has been added. This allows Quarkus developers to get enhanced editing experience to Qute templates located in their projects.

A Qute template is any file located under src/main/resources/templates and with the html, yaml, yml, json or txt extension.

Qute support is enabled on any project that has a dependency on the Qute library.

You can generate a Qute enabled project with the Quarkus project wizard and choosing the RESTEasy Classic Qute extension

Features included into the Qute support are:

Any reference to a Qute template file from a Java file show the option to generate the Qute template file (if the Qute template file has not been found in the project) or navigate to the Qute template file.

The Qute language server has support for built-in and user-defined Java classes, including parameter completion and validation for their methods. Take advantage of this to easily avoid Java related mistakes.

When hovering over an expression in a Qute template, the Java type (built-in or user defined) will be displayed.

Similar to most language, linked editing is now supported for Qute templates , allowing for simultaneous renaming of multiple parameter expressions.

Qute templates use sections in its templating language to power any logic required when compiling and displaying the resulting document. To support this, the extension’s Qute support populates a completion list with all available Qute sections, along with any parameters they take and a small code snippet of its usage.

Java and Qute validation is included for Qute templates with Quarkus Tools, including diagnostics and quick fix suggestions.

The developer has the ability to disable this validation in their settings through the Window → Preferences → JBoss Tools → Qute.

The second table contains a list of Qute templates (as regular expressions) for which validation will be excluded.

If any of the available validation is disturbing your development, you can disable Qute validation for the file project with a single click, using a “Quick Fix” that appears on every Qute related diagnostic

Paired with corresponding Java methods, built-in Java classes also have built-in Qute value resolvers made available by the Qute templating engine that is evaluated and outputs, or resolves to, a value. Quarkus Tools supports completion, hover and snippet generation for these built-in value resolvers.

Template extension methods are used to extend the set of accessible properties of data objects. Qute support in Quarkus Tools has support for marked @TemplateExtension Java methods, which extend a given data model.

A CDI bean annotated with @Named can be referenced in any template through cdi and/or inject namespaces. Quarkus Tools provides completion and definition navigation support for Beans.