Hi Mohit, 2014-04-08 23:57 GMT+02:00 Mohit Jaggi <[email protected]>:
> Hi Folks, > I am trying to find a way to run the jooq code generation in an automated > fashion on a build server. I do not want the build to try and connect to a > DB to get the schema. Is there a way to supply the schema to jooq code > generator in a file or something? > There are a couple of feature request that go into this direction: - Support generating code based on JPA annotations ( https://github.com/jOOQ/jOOQ/issues/2899) - Various ideas around a code generation plugin architecture ( https://github.com/jOOQ/jOOQ/issues/1464) 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. 2014-04-09 0:59 GMT+02:00 Rob Sargent <[email protected]>: > At some point the developers need to check in the generated code, building > against the schema built up by flyway, mybatis, ruby-activeRecord or > whatever. The build system then gets the generated code along with the > rest of the code, no? > That's another very good option, although many people would claim that generated code should not be checked into the version control system. This depends on your taste and your existing build strategies. Cheers 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]. For more options, visit https://groups.google.com/d/optout.
