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.

Moving extensions outside of core repository

See original GitHub issue

Proposal (with question marks for the ones I’m really not sure about):

amazon-alexa
amazon-services
artemis-core
artemis-jms
consul-config?
jgit
jsch
logging-gelf
logging-json -> this one, I think we should just decommission it: we have another logging-json extension in the Quarkiverse with more features
logging-sentry
narayana-stm?
tika
vault? (@vsevel do you see a good reason to keep it in Core?)

Questions:

should we change the groupId to io.quarkiverse?
should we change the root package to io.quarkiverse?
should we change the version? Using the Quarkus version scheme might be confusing with compatibility (e.g. we have a 1.13.3.Final extension but it’s indeed also compatible with Quarkus 2).
what do we do if some of these extensions are used by the Platform? Typically I wonder if jgit isn’t used by Camel Quarkus.

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:44 (40 by maintainers)

Top GitHub Comments

5reactions

michael-simonscommented, Jan 20, 2022

Hey. Just to let you know: after the first releases has been cut from the Neo4j quarkiverse extension, they way it still is on code.quarkus.io I have to say I’m sold on the solution. Great way forward for both 3rd party vendors and Quarkus. Well done.

1reaction

gsmetcommented, Feb 28, 2022

I did the first batch. I think we can close this one and open a new one should we move others.