I believe I've run into a bug in the Jooq Maven plugin (jooq-codegen-maven).
It seems to me that outputSchemaToDefault flag is not interpreted
correctly during code generation when it is triggered via the maven plugin.
I am running 3.5.3 of the jooq maven codegen plugin as well as jooq itself.
The code generation snippet in the pom file looks something like this.
<generator>
<name>org.jooq.util.DefaultGenerator</name>
<database>
<name>org.jooq.util.derby.DerbyDatabase</name>
<includes>.*</includes>
<schemata>
<schema>
<inputSchema>public</inputSchema>
*
<outputSchemaToDefault>true</outputSchemaToDefault>*
</schema>
<schema>
<inputSchema>analytics</inputSchema>
<outputSchema>analytics</outputSchema>
</schema>
</schemata>
</database>
<target>
<packageName>com.foo.model</packageName>
<directory>target/generated-sources/jooq</directory>
</target>
</generator>
I expect code generated for the public schema to be in package
*com.foo.model*.
Instead they end up being in *com.foo.model._*
It seems to be that the maven plugin interprets this the output schema to
be blank and appends an underscore because it is an invalid package name.
This looks like a bug to me, unless there is a user error on my end.
--
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.
