-
The goal is to have the records generated some way. TBD
-
### Description
We should leverage the benefits of Quarkus extensions for our components as there can be made certain optimizations during a build time. At this moment, we use directly `picocli` d…
-
### Description
The idea of this extension is analogous to the Maven Enforcer Plugin: introduce Build Items to control certain environmental constraints such as Quarkus version, JDK version, and OS…
-
### Current Behavior
Having to deal with multiple tech stacks (Alpine for API server, Quarkus for all other services) poses some challenges. It would be great if we could eventually converge them all…
-
Coming from https://github.com/apache/incubator-kie-issues/issues/909
- Rename the extensions artifacts as agreed in the [spreadsheet](https://docs.google.com/spreadsheets/d/1gsttRcXGtwGQO469EYFD…
-
### Description
We would like to propose to build a new Quarkiverse extension to enable Zenoh support for Quarkus. We probably would like to do something along the likes of the MQTT extension with Sm…
-
### Description
Currently when a quarkus extension brings in a CLI plguin, the name of the plugin is configured in the extension metadata.
Extension developer need to align the alias used with the r…
-
We currently have some Quarkus apps running natively that uses the oficial "amqp-client" dependency. Comparing the example code to what we currently have, both seems quite similar, except the part whe…
-
I'm using the IntelliJ Quarkus Tools 1.30.1 with a Qute example project: https://github.com/mkouba/qute-insights
I can navigate from the HelloResource to the template hello.html, but in the hello.h…
-
Title (proposed): The basics, tips and tricks of creating your own Quarkus extensions
Description (proposed): XXX
Guests: Holly Cummins, Emil Lefkof (Melloware), + ??
Twitter: XXX