You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 28, 2024. It is now read-only.
Having to pass an XML config file to jOOQ makes it hard to dynamically compute values in the jOOQ configuration such as absolute paths of output directories; you end up needing to generate the XML file before calling the plugin.
The officially-blessed jooq Gradle plugin supports dynamic configuration of the code generator. So one solution would be if Jooq-Modelator could optionally delegate the codegen step to that plugin, while still managing the migrations and the Docker container.
Or perhaps the plugin could allow the build script to supply a generator config object constructed using jOOQ's programmatic configuration API.
The text was updated successfully, but these errors were encountered:
thank you for your input. This indeed could be useful. I'm not sure when I will find the time to work on such a feature. If you want to contribute, I'm happy to help, and I do accept pull-requests.
There is a plugin similar to jooq-modelator which does support the dynamic configuration you are looking for. Maybe this can solve your problem? Here is the link.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Having to pass an XML config file to jOOQ makes it hard to dynamically compute values in the jOOQ configuration such as absolute paths of output directories; you end up needing to generate the XML file before calling the plugin.
The officially-blessed jooq Gradle plugin supports dynamic configuration of the code generator. So one solution would be if Jooq-Modelator could optionally delegate the codegen step to that plugin, while still managing the migrations and the Docker container.
Or perhaps the plugin could allow the build script to supply a generator config object constructed using jOOQ's programmatic configuration API.
The text was updated successfully, but these errors were encountered: