I did do the globalTableReferences thing. It at least eliminates the
annoyance I was feeling whenever I wrote some JOOQ code - I *knew* I was
using thing inconsistently but I didn't want to setup a static analysis
tool. I didn't really care which one was used (though it was confusing and
annoying at first when figuring out that it didn't matter).
When I tried to do the globalObjectReferences instead, I ran into a problem
with Sequences - the global object ref is the *only* specific code
reference JOOQ generates.
One thing I did do in my own project structure was to factor out the JOOQ
generated code to its own Gradle sub-project that my server depends on.
This helps me quickly filter out all the JOOQ internal references when I'm
scanning the results in my IDE.
I have "pojos=false", so now I do searches by looking for:
- Example() ctor
This works well enough for me.
Thanks for your help.
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].