Thanks everyone, for sharing their thoughts! > Separate module is not a convenient way. > [...] > I don't want to create a separate module for any new project for only this > feature.
I understand. Yet, creating a dedicated module seems to me the path of least resistance. You could, of course, build jooq-codegen yourself and add your own strategy as a part of jooq-codegen directly in there. Then you wouldn't have any issues with these dependencies. > For my purpose, i want to change only the name of the Factory to application > name. Then again, you can extend the generated [Schema]Factory and use that instead. > Lukas, what about rules tags > like http://sourceforge.net/apps/trac/jooq/ticket/1171 ? As the custom generator strategy turns out to be the most powerful solution I could provide to users, #1171 is now at a lower prio. I wonder whether supporting scripting languages, such as velocity, wouldn't be much better than extending the strategy and Java-based source code generation so much. Patches / implementation drafts for #1171 are welcome, of course! Cheers Lukas
