jooq for Quarkus

[tod...@googlemail.com]

Hi,

there is an open issue for jooq support in Quarkus. https://github.com/quarkusio/quarkus/issues/7440

Today I try to bump this thread a little bit and it turns out, that the guys from Quarkus seems to be interested (in the meantime) to add support.

BUT ... they're looking for someone who maintains the needed Quarkus extension (similar to the Spring Boot Autoconfiguration).

There is an already existing version https://github.com/leotu/quarkus-ext-jooq a little bit outdated but maybe a good starting point.

Is anybody out there who can try their very best  ?

Or, hey, Lukas, maybe you ?

Kind regards

Dominik

[Lukas Eder]

Hi Dominik,

Thanks for the ping. I'm following this issue with great interest and can only encourage you and the community to go forward with this. I'll be happy to help or answer questions on any issue tracker for jOOQ related questions, however, I cannot currently maintain such an integration. See, there are so many of these Quarkuses out there. If Data Geekery was a huge corporation with a lot of devrel and community building staff, we'd be integrating with all of:

- Gradle

- SBT

- Ant (?)

- Quarkus

- Spring Boot

- Typesafe Activator

- Lagom / Akka

- Vertx

- Azure

- AWS

- Graal AOT

- Ktor

- Various Java EE containers (they're still a thing!)

- Spark Java

- Grails

- Micronaut

- Play Framework

- Ninja Framework

- ... and more

Alas, we're not this huge corporation. We want to focus on jOOQ and SQL awesomeness, and let the integrators do their integrator job. Ultimately, if Red Hat wants to own such a platform, then they will have to go the route of Spring Boot and Micronaut, and maintain the integrations - at least that's my opinion. 

I know that Typesafe historically didn't seem to want to push too many third party integrations themselves, because their stack is very opinionated towards their own products, and because jOOQ competes with Slick / Anorm respectively, and because jOOQ is pure Java, whereas Typesafe still has their historic relationship with Scala (we all know that resistance to jOOQ is futile, but here we are 😉)

We'll see what Red Hat will do about this. I will certainly be available for questions and can handle some community support if the problems are jOOQ related (I'm doing that as well with the Gradle plugin by Etienne Studer: https://github.com/etiennestuder/gradle-jooq-plugin).

In any case, thanks a lot for pushing this!

Lukas

--
You received this message because you are subscribed to the Google Groups "jOOQ User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jooq-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/7d79af69-d1d7-4fa5-9ae0-88c5d5969e28o%40googlegroups.com.

[Lukas Eder]

For the record, I've created a poll to gather more community feedback about the integration:

https://twitter.com/JavaOOQ/status/1271372119985831937