> I just checked out the Xtend code generator and I do have to say it is > easier to understand
I agree, it looks more intuitive. > Right now I tried to look into using jOOQ's code generator to just generate > simple static String constants for table and column names that have no jOOQ > dependency. > String constants are nice because you can use them in Annotation arguments. > When you regenerate the code string constants from the database and your > code doesn't compile then you know that there is a mismatch. That's a good idea > I looked at the generator (albeit briefly) but felt like I would have to > almost rewrite the generator to do such. Yes, today's code generator is an organically evolved mess. As I said, I'll happily look into Aaron's generator API re-engineering suggestions. I feel that a formally supported and extensible public generator API will be a big plus in jOOQ 3.0. Re-engineering this API is independent from using Xtend, though. You will still be able to implement overriding elements using Xtend. In any case, don't be discouraged by my decision not to use Xtend. Feel free to publish, maintain and support your own generator implementation. If you wish, I can then reference to such an inofficial generator implementation from the jOOQ website. Cheers Lukas
