Hm, following Lukas's suggestion you'll be writing code to generate and later read a file, checking that in and reading it on the build machine to generate the jooq classes to build your app. Doesn't seem worth it to me. Checking them in let's them evolve naturally.
Sent from my iPhone On Apr 12, 2014, at 2:23 PM, Mohit Jaggi <[email protected]> wrote: >> >> >> Already today, you can implement your own jOOQ-Meta Database that supplies >> schemas, tables, columns, etc. to the code generator. This custom Database >> could read any sort of XML file, e.g. an external one by Flywaydb or >> Hibernate. >> >> How you generate that external file would then be entirely up to you. > Lukas, > I did not understand. Could you please point me to an example or section of > jooq documentation please? > > Rob, > For the time being I am adding generated code to git repo, which I don't like > much. > > Thanks, > Mohit. > -- > 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. -- 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.
