jnturton commented on issue #2882:
URL: https://github.com/apache/drill/issues/2882#issuecomment-1965733063
Hi. To this day, every binary distribution of Drill released by the project,
including the published Maven artifacts, maintains JDK 8 compatibility. Even
when that distro is bundled
cgivre merged PR #2879:
URL: https://github.com/apache/drill/pull/2879
--
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
Der-Joscha commented on issue #2882:
URL: https://github.com/apache/drill/issues/2882#issuecomment-1965231451
Is there anything I should have done except changing `maven.compiler.source`
and `maven.compiler.target` to 17?
With this configuration, it seems, that `--add-opens
cgivre commented on issue #2882:
URL: https://github.com/apache/drill/issues/2882#issuecomment-1964358761
@Der-Joscha One thing... Drill's JDBC driver is located here [1]. You might
try building and running that yourself with Java 17 and seeing if that works.
[1]:
cgivre commented on issue #2882:
URL: https://github.com/apache/drill/issues/2882#issuecomment-1964350759
@Der-Joscha This is the right place, and we can help you out with this. I'm
wondering if we are simply not updating what is in maven.
--
This is an automated message from the Apache
Der-Joscha commented on issue #2882:
URL: https://github.com/apache/drill/issues/2882#issuecomment-1964342062
Thanks for your fast reply, I did not find an alternative artifact in the
mvnrepository that indicates it is made for java 11 or 17.
Do you know who I can ask, if this is not
Der-Joscha opened a new issue, #2882:
URL: https://github.com/apache/drill/issues/2882
Hello,
I am currently working on an application with java 21 that uses the jdbc
driver from drill to execute distributed sql queries.
Since the module system was introduced with Java 9, we get
