CASSJAVA-135 Update the build to use Java17 rather than Java8

[absurdfarce]

Replaces #2096

[absurdfarce]

Jenkins run on this new branch was also green (minus the PointIT issues which should be addressed by #2097)

[absurdfarce]

Ping @tolbertam for visibility after moving to a new PR

[SiyaoIsHiding]

This will break ASF CI, right?

[absurdfarce]

Hmmm, we might need to make some changes to the ASF CI to get it to build with Java17 as a default. But we probably need a general cleanup there anyway since I don't think the Java25 changes included any updates to the ASF Jenkinsfile either.

Might be worth just having a general "update the ASF CI" PR once this goes in.

[SiyaoIsHiding]

What do I need to do locally to run mvn clean install -DskipTests -Dmaven.javadoc.skip=true;? I checked out your branch, switched to java 17, but then got

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.15.0:compile (default-compile) on project java-driver-core: Fatal error compiling: error: release version 17 not supported -> [Help 1]

[absurdfarce]

Are you sure you switched to Java17 @SiyaoIsHiding? We switch to using the maven.compiler.release property in this PR since that's the standard way of notating this for "newer" JDKs (by which they apparently mean anything older than Java9). The error you're seeing seems to suggest that your javac version can't support "-release 17" which in turn makes me think you might still be using an older JDK.

To validate I executed mvn clean install -DskipTests=true in the core directory using Java11 and got exactly the error you cited. Switching to Java17 immediately resolved the issue.

[SiyaoIsHiding]

You are right! Turns out because I have both jenv and sdkman installed, my java environment was a bit messed. I can compile the project with java 17 succesfully now.