Hi Thomas, Thanks a lot for pointing this out to us. This makes perfect sense, but it's currently not possible, as "immutability" has been seen as a POJO feature only, in case of which the interfaces are adapted as well as a side-effect. It would make sense to add a new flag "immutableInterfaces", which is turned on automatically once "immutablePojos" is set. I have registered a feature request for this: https://github.com/jOOQ/jOOQ/issues/5327
In the meantime, a workaround would be to post-process the generation output and remove all the generated POJOs, or skip POJO generation in your own custom JavaGenerator override. Hope this helps, Lukas 2016-06-01 15:12 GMT+02:00 <[email protected]>: > Hello, > > When generating artefacts from my database, I need to generate immutable > interfaces for use in not-jooq-aware modules, but I'm not interested at all > in POJOs (records are enough). > It seems it's not possible to generate these immutable interfaces without > the POJOs, since the only immutable-related setting is "immutablePojos", > which is implying "pojos". > > Maybe I could do it with a custom generator implementation, but > nevertheless I feel like the generator is missing an "immutableInterfaces" > setting. > I was about to create a new GitHub issue, but I'm asking here first in > case I missed something obvious. > > Thanks, > Thomas > > -- > 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.
