At the recent JAX conference, I had an interesting discussion with Peter Verhas, another speaker. In principle, it would be possible to generate jOOQ classes during the Maven test phase, assuming that phase will never be skipped. At that point, all the ordinary classes are already available, and jOOQ's JPADatabase could be introspecting them using the existing mechanisms. The jOOQ generated code would obviously end up in the test target directory, and would have to be included in the ordinary jar file using some workaround.
This is a hack, but perhaps one that works sufficiently well. Lukas On Tuesday, January 2, 2018 at 4:31:17 PM UTC+1, Lukas Eder wrote: > > > > 2018-01-02 16:22 GMT+01:00 Denis Miorandi <[email protected]>: > >> Hi Lukas, tks for your honest answer about priority. I really appreciate >> it. >> I would like to examine in depth apt generation to have obtain new hints >> about this I'll eventually wrote it in github issue. >> > > Cool, thank you very much for your help! > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jooq-user/a0485350-01d6-4435-9b79-c0af87cea3ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
