Hi Marco, Thanks for your message. jOOQ 3.10 is the first minor release that is formally integration tested with Java 9 and Java 10. There were also a few fixes related to JAXB that will make the integration easier moving forward (only in jOOQ 3.11, I think).
The error you run into is a known "regression" for all libraries that do re-use packages (bad idea regardless of JPMS), but since jOOQ is not yet modularised, this should not cause issues to my understanding. How did you run into this, i.e. how can this be reproduced? And can you still reproduce it with jOOQ 3.10? For the record, jOOQ 3.11 should rename packages in jOOQ-meta and jOOQ-codegen to prevent this kind of problem [1], also as a prerequisite to actually modularising jOOQ [2]. Thanks, Lukas [1]: https://github.com/jOOQ/jOOQ/issues/7419 [2]: https://github.com/jOOQ/jOOQ/issues/4699 2018-04-15 22:36 GMT+02:00 <marco.dubac...@gmail.com>: > When using jooq with java 10 I get the following compile time error: > > Error:java: the unnamed module reads package org.jooq.util.sqlite from > both jooq and jooq.meta > > I guess the problem is unrelated with java 10 but relates with the JPSM > starting from java 9 on. > > Do I have to upgrade from jooq 3.6.1 to jooq 3.10.X to fix this problem? > > Cheers > Marco > > -- > 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 jooq-user+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 jooq-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
