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
I think it would be more clear to put jOOQ stuff inside a jOOQ element. I'm aware that this would produce an apparently unnecessary additional level of nesting, but:
Even in jOOQ, <generator/> isn't a top level element. While <jdbc/> isn't necessary in most cases, it may be in some (e.g. to pass additional properties to the JDBC connection)
There are elements like <skip/>, <logging/>, <onError/>, <onUnused/>, <configurationFile/>, and others that might be added in the future, which you won't support out of the box unless you nest jOOQ's configuration in a <jooq/> element. Note, you could add support for these in your own top level, but then that would be confusing as it wouldn't be clear if e.g. <skip/> belongs to jOOQ, or to you.
Who knows if you're going to add more additional elements in the future, e.g. to clean up / post-process generated code, etc. Those elements will also possibly conflict with jOOQ stuff.
The text was updated successfully, but these errors were encountered:
Hi @sivaprasadreddy , @lukaseder .
I like suggested approach.
Actually I'am already looking on possible solutions.Not sure that it will be completed by monday, possibly by the end of next week.
The plugin configuration looks like this:
I think it would be more clear to put jOOQ stuff inside a jOOQ element. I'm aware that this would produce an apparently unnecessary additional level of nesting, but:
<generator/>
isn't a top level element. While<jdbc/>
isn't necessary in most cases, it may be in some (e.g. to pass additional properties to the JDBC connection)<skip/>
,<logging/>
,<onError/>
,<onUnused/>
,<configurationFile/>
, and others that might be added in the future, which you won't support out of the box unless you nest jOOQ's configuration in a<jooq/>
element. Note, you could add support for these in your own top level, but then that would be confusing as it wouldn't be clear if e.g.<skip/>
belongs to jOOQ, or to you.The text was updated successfully, but these errors were encountered: