Using the javax.xml.ws made sense to me since I avoided using a deprecated or internal library from Java. I don't like that I still used "--add-modules java.xml.bind" for CodeGen, as it doesn't remove this dependency going forward.
Your solution still makes use of sun packages, which I think it would be better to avoid. I actually put javax.xml.bind/jaxb-api in my pom.xml file as well, but it didn't seem to help out. On Monday, October 22, 2018 at 4:39:43 PM UTC-4, Marshall Pierce wrote: > > Oops, I misspoke -- jaxws-rt has those three transitive dependencies; > jaxws-api only has some of them. > > On Monday, October 22, 2018 at 2:26:45 PM UTC-6, Joseph Dornisch wrote: >> >> So, I'm updating my own small project from java 8 - currently to 9 and >> will move to 11 later today. >> >> In order to generate the jooq source (which I don't do via maven >> currently, I added '--add-modules java.xml.bind' to the command: >> java --add-modules java.xml.bind org.jooq.codegen.GenerationTool >> codegen.xml >> >> Then to compile my code along with the generated code, I added the >> following dependency to my pom.xml file: >> <dependency> >> <groupId>javax.xml.ws</groupId> >> <artifactId>jaxws-api</artifactId> >> <version>2.3.1</version> >> </dependency> >> >> Is this the generally preferred way of moving forwards with jooq with >> java 9,10,11 right now? >> Is there some other replacement dependency I should use for code >> generation similarly to adding the javax.xml.ws dependency? >> >> Sorry, if this is covered elsewhere, I did try to find information in the >> online jooq documentation. >> >> Thanks. >> > -- 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.
