I see, thanks for the clarification. I've just noticed that our integration tests only cover running jOOQ on the classpath, not on the module path. This is of course a significant flaw in our tests (your issue would not have gone unnoticed that way). I will fix this right away.
Notice also that I've already fixed your issue for jOOQ 3.11: https://github.com/jOOQ/jOOQ/issues/7419 As this includes renaming packages, which is quite a significant backwards incompatibility, the fix will not be applied to earlier minor releases. However, you should be able to work around the problem. Only the code generator is affected by this problem, not the runtime. You can create a separate project / maven module that takes care of code generation. That project / module should not be on the module path (and doesn't need to, as that module won't depend on the new http client). It generates the code only, which works under Java 9 and 10. Your runtime project / module can then be on the module path and include only jOOQ as a dependency, not jOOQ-meta nor jOOQ-codegen. Does this work for you? Thanks, Lukas 2018-04-16 15:57 GMT+02:00 <[email protected]>: > Addendum: I guess my problem can not be solved.... => > https://stackoverflow.com/questions/48871059/muting- > java-9-split-package-errors-on-intellij > > -- > 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. > -- 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.
