I'm sorry for the delay. This appears to be a bug in the code generator.
I've registered an issue for this:
Thank you very much for reporting. A workaround could be perhaps running
two separate code generation runs and merging the contents into the same
directory using the Maven resources plugin, for instance...
2016-10-17 15:36 GMT+02:00 Kai Waldron <kaiwald...@gmail.com>:
> Bump. Anyone have any ideas?
> On Tuesday, October 11, 2016 at 3:33:49 PM UTC-6, Kai Waldron wrote:
>> Using Jooq version 3.8.4:
>> Scenario for this is a jooq.xml that has a the following generator
>> Issue I'm seeing is when the "model" schema has outputSchemaToDefault set
>> to true, the master schema gets generated (if I watch the file system), and
>> then deleted. The "model" schema does get generated to the _ directory.
>> If I comment out <outputSchemaToDefault>true</outputSchematoDefault> the
>> master schema generates correctly and is not deleted, but then of course
>> the model schema is now qualified with model..which we don't want. Any
>> ideas on how to get this combination to play nicely together?
> 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 jooq-user+unsubscr...@googlegroups.com.
> 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
For more options, visit https://groups.google.com/d/optout.