Proper way of setting up extension that uses other Quarkus dependencies #40847
Unanswered
ThomasKluiters
asked this question in
Q&A
Replies: 1 comment
-
Hey @ThomasKluiters, Glad to hear you love Quarkus. Sorry, we are a bit slow at the moment as a lot of us are in Slovenia for JCon. So I don't entirely know how the Quarkus OpenAPI Generator actually works but here are a few hints on how we integrate extensions with each other:
So in short: maybe there's nothing to do except push the classes to the Jandex index, maybe there are integration points that you can use in the extension and maybe you will need more but, in this case, better ping the OpenAPI generator team in an issue (and give a lot more details so that they can figure out what you need). HTH! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
I've been using Quarkus for a good while now. Super happy with it and absolutely LOVE it!
I'm trying to develop my own quarkus extension, though, I'm running into some issues - structuring my project seems quite difficult.
I want to use the following quarkus plugin: https://github.com/quarkiverse/quarkus-openapi-generator to generate some Api clients for my extension. However, this requires me to edit my plugins in the runtime module, and I don't think this is the intention. Is there any suggested approach to set up an extension that leveraging code generators?
Beta Was this translation helpful? Give feedback.
All reactions