On Wednesday, October 24, 2018 at 2:10:21 AM UTC-4, Lukas Eder wrote: > > Be careful, though. Version 2.3 is modular, which can cause other problems > on JDK 8, in case you distribute to that version of the JDK as well. > > Having said so, one of the reasons why I haven't documented all of this is > because the correct setup - very unfortunately - depends on what else is on > your classpath. For example, this is the first time I've seen someone have > a jaxws-api dependency as well. Things might be just a bit different once > that dependency is on the classpath, than when it is not. > > jOOQ 3.12 will declare the JAXB API dependency and provide its own "mini" > implementation that will be used in the absence of a JAXB implementation on > the classpath. I do hope that in some more distant future, jOOQ will be > able to do without JAXB entirely. > > I don't know what to make of your statement about the jaxws-api dependency, because if I do not have it the generated code does not compile:
[ERROR] /C:/Users/jad292/Dropbox/testcode/alcuin/src/main/java/com/alcuin/generated/jooq/tables/records/StockDayRecord.java:[11,13] package javax.annotation is not visible (package javax.annotation is declared in module java.xml.ws.annotation, which is not in the module graph) [ERROR] /C:/Users/jad292/Dropbox/testcode/alcuin/src/main/java/com/alcuin/generated/jooq/tables/records/TestRecord.java:[9,13] package javax.annotation is not visible Maybe there's a better package to include to get javax.annotation, and I don't really have a 'jaxws-api' dependency, as i would think this would be pretty common in jooq related projects. Or maybe I'm using some old form of codegen.xml? Right now I'm using an h2 database. -- 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.
