I see. Well, this particular set of regressions just shows how great Java's backwards compatibility used to be, which we always took for granted :-)
It also shows why you're the first to bring this up on the jOOQ mailing list. Because no one is really using Java 9 or 10 yet, for these reasons. Which ones are the libraries that cause issues? There's a discussion on the Java Champions mailing list right now, with quite a few people criticising Oracle for JPMS. This particular regression seems quite severe, and I haven't seen that being discussed often enough yet. Cheers, Lukas 2018-04-19 22:02 GMT+02:00 <marco.dubac...@gmail.com>: > Thanks for your help and your fix in jOOX 3.11. > > Your workaround would indeed fix the problem as far as jooq is concerned > but there are unfortunately some other libraries on my module path which > have an issue regarding split packages. > > Cheers > Marco > > > > On Thursday, April 19, 2018 at 1:36:34 PM UTC+2, Lukas Eder wrote: >> >> 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 <marco.d...@gmail.com>: >> >>> 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 jooq-user+...@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. > -- 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.
