Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Remove 'vertx', 'quarkus' from module/image names

See original GitHub issue

With spring boot variants removed (#3090) the adapter maven module and image names can be shortened. I guess the “vertx” part can be removed as well. E.g. renaming hono-adapter-amqp-vertx-quarkus to hono-adapter-amqp.

Issue Analytics

State:
Created 2 years ago
Comments:13 (13 by maintainers)

Top GitHub Comments

1reaction

calohmncommented, May 20, 2022

Naming is a bit tricky then, though. We currently have

hono-adapter-base in directory adapter-base containing adapter base classes
hono-adapters in directory adapters: container module for the adapter modules
hono-adapters-quarkus in directory adapters/base-quarkus, containing dependencies and build profiles, used as parent of the actual adapter modules.

Renaming hono-adapters-quarkus to hono-adapters-parent then?

1reaction

sophokles73commented, May 6, 2022

I think keeping support for Hono 1.x images would require keeping some 1.x-only logic in the Hono Helm chart,

I would rather get rid of all of the deprecated stuff and have a clean 2.0.0 based chart. As you pointed out, users who want to stick to Hono 1.x can still use the 1.x based chart. FMPOV we should strip out everything that is no longer supported in Hono 2.0.0 from the chart as well.

Top Results From Across the Web

Vert.x Reference Guide - Quarkus

Vert.x is a toolkit for building reactive applications. As described in the Quarkus Reactive Architecture, Quarkus uses Vert.x underneath.

Using Eclipse Vert.x API from a Quarkus Application

As described in the Quarkus Reactive Architecture, Quarkus uses Vert.x ... Our VertxResource will send a message containing a name to the greetings...

All configuration options - Quarkus

AWS Lambda Type Default AWS Lambda Common Type Default AWS Lambda Gateway REST API Type Default Agroal ‑ Database connection pool Type Default

Using Reactive Routes - Quarkus

Reactive routes propose an alternative approach to implement HTTP endpoints where you declare and chain routes. This approach became very popular in the ......

Writing REST Services with RESTEasy Reactive - Quarkus

RESTEasy Reactive is a new JAX-RS implementation written from the ground up to work on our common Vert.x layer and is thus fully...