Red Hat build of Quarkus 3.x Component Details

The page lists important details about the Red Hat build of Quarkus Components used in Red Hat Application Runtimes. Refer to the Red Hat Application Runtimes Component Detail Index for other releases[1].

Level of Support Classifications

Module support classifications serve as guidelines for customer use cases, and they are described in detail below:

• S
  The component fully supported for usage both in JVM and Native mode
  As defined by the Red Hat Production Support Scope of Coverage.

• JVM
  The component fully supported for in JVM mode, Native mode are considered as Tech Preview
  As defined by the Red Hat Production Support Scope of Coverage.

• D
  The component has been marked as deprecated and might be removed in the next release, but it's still supported in this release
  As defined by the Red Hat Production Support Scope of Coverage.

• TP
  The component is considered a technology preview. Red Hat does not provide support for Technology Preview components provided with this release of Red Hat build of Quarkus. Items designated as Technology Preview in the sections below have limited supportability, as defined by the Technology Preview Features Support Scope.

• DEV
  The component is supported for development use only as defined by the Red Hat Development Support Scope of Coverage

• DP
  The component is provided as developer preview as defined by the Red Hat Developer Preview Scope of Coverage

Bill Of Material (BOM) with supported and none supported extensions

For convenience purposes Red Hat build of Quarkus ships with two different BOM files. One that only includes productized extensions and one that contains both productized and community extensions. Please note that the purpose of a Bill of Material is to align versions within a release to avoid misalignment of versions and as such it's not optimal to list supported vs not supported extensions. For a complete list of supported extensions please check the dedicated table on this page.

We only support application build using a BOM, please use one of the following Bill of material:

List of the available platform versions

Red Hat build of Quarkus 2 and later is using a platform concept to align multiple groups of extensions. The list below shows which platform vesions have been released and the members list which additional groups of extensions has been included.

Supported extensions in Red Hat build of Quarkus 3.x

The maven dependency need to use the groupID io.quarkus.
We recommend to use the bom file instead of adding the dedicated version for the component.

NOTE: Some of the extensions were renamed between 3.8.6 and 3.15.1. For technical reasons they appear twice in the table below: under the old name (and marked as supported in 3.8 versions ) and under the new one (and marked as supported in 3.15 versions). Details can be found in release notes for SmallRye Messaging and RESTEasy Reactive extensions.