> @Dominik, how did you added them for plugin classpath?
As Lukas wrote, your entities have to be on the classpath as well. For me
the following gradle script worked to generate the JOOQ metadata classes:
buildscript {
repositories {
mavenCentral()
jcenter()
}
dependencies {
classpath("nu.studer:gradle-jooq-plugin:1.0.6")
classpath("org.jooq:jooq-meta-extensions:3.8.4")
classpath files('bin')
classpath("org.springframework.boot:spring-boot-gradle-plugin:1.4.1.RELEASE")
}
}
As I was working with Eclipse, the class files of my JPA Entities got
stored in the bin directory. If I use this declaration, then the schemas
public_ and information_schema are handled. The entity classes are then
contained in package com.example.jooq.public_.tables.
As you might be interested in the public schema only, you could restrict
the metadata generation to this schema by defining the inputSchema property
to 'PUBLIC' in the jooq.generator.database section:
database {
name = 'org.jooq.util.jpa.JPADatabase'
properties {
property {
key = 'packages'
value = 'com.example.model'
}
}
inputSchema = 'PUBLIC'
}
With this definition the JOOQ metadata of my entity classes were generated
in package com.example.jooq.tables.
Hope this helps. However I have to add the comment that I also get errors
if newer versions of the plugins are used. I originally had defined the
dependency to the jooq plugin as nu.studer:gradle-jooq-plugin:+, but at
some day the build did no longer work (as the newest version of the plugin
was used).
Best wishes
Dominik
--
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.
