Hi Ben, Hard to say what's causing this. We don't generate jakarta annotations yet, so maybe that's it? https://github.com/jOOQ/jOOQ/issues/9641
Do you really need bean validation on our generated POJOs? In the past, I've thought about deprecating this kinda weird feature. I'd love to hear about use-cases On Sun, Sep 26, 2021 at 12:27 AM Benjamin Greiner < [email protected]> wrote: > I have an entire sample project built I can zip up and include if you like > to test with. Please let me know. If you think there's a bug in jOOQ other than the above wrong annotation namespace, why not? You can submit it here: https://github.com/jOOQ/jOOQ/issues/new/choose -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/CAB4ELO6xq%2BmCQrMDETsnDhjK7WuYFoxE%2BN3Mqx%3DqEmS88cOrmQ%40mail.gmail.com.
