Der-Joscha commented on issue #2882: URL: https://github.com/apache/drill/issues/2882#issuecomment-1968695683
According to my build system, it is an [automatic module](https://docs.oracle.com/javase/specs/jls/se17/html/jls-7.html#jls-7.7.1) generated from drill-jdbc-1.12.0.jar. As soon, as I am using a `module-info` for my own application, it is created (and must be `requried`) by the module system. While this works with drill-jdbc (as long as the jvm is invoked with `--add-opens java.base/java.lang=ALL-UNNAMED`), when using drill-jdbc-all instead, the automatic module is not found and omitting it in the `module-info`leads to the following compile error: `package org.apache.drill.jdbc is not visible`. Is there a serious disadvantage, if I use drill-jdbc instead of drill-jdbc-all? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@drill.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
