Hm. 

Our beans live in a module by themselves.

I want to bind the enums in that module to use our existing enum type.

In order to reference the generated jooq enum types, the converters need to 
be in the same module as the generated code.
That is, they cannot reference the generated enum until it exists, and the 
generator won't compile without the converter types properly resolved.

Unless it is possible to generate the enum types first in one module, then 
reference them in a later module which registers converters, I am in a bit 
of chicken-and-egg problem.
That or I don't understand how to tell jooq to just straight up use my enum 
entirely and not own it's own copy (which I can't reference in converter 
until it exists, and can't generate without my converters on classpath).

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to