Quarkus integration

[lw-mcno]

First of all, thanks for providing and maintaining this useful library.

Are there any plans of supporting a Quarkus integration?

[lukas-krecan]

Hi, thanks for feedback. There are no such plans since I am otherwise engaged. If you need it, you can implement it yourself. With Quarkus interceptors it should be quite easy. You can use the Micronaut implementation as an inspiration. It's just few classes. If you do that, please send PR, I will be happy to merge it.

[lukas-krecan]

POC is here https://github.com/lukas-krecan/shedlock-quarkus

[lukas-krecan]

Rundimentary support will be part of 5.0.0 release

[dcdh]

Hello all, I am doing some work on it.
You can have a look to this PR: quarkiverse/quarkus-shedlock#3

Regards,

Damien

[lukas-krecan]

@dcdh There already is CDI integration tested with Quarkus. Is there anything missing that would justify creating a new project to do the same?

[dcdh]

I guess yes.
I have added build time code to avoid declaring beans by ourself.
A developer can just add an annotation to make it works without producing expected LockProvider. It is done out of the box.
I've keep the same module hierarchy (providers and next specifique ones)

Regarding Jdbc, a developer can specify the datasource to use and the extension will validate it at build time (check that specified datasource existe).
Moreover, regarding table création I could not rely on ShedLock jdbc template dependency because I do not want to add Spring jdbc dependency inside a Quarkus application. So I have redevelop an initialiser bound one each datasource used.

The developer can use multiple providers if needed.