Jon Haddad created CASSANDRA-19449:
--------------------------------------
Summary: Support building with JDK17
Key: CASSANDRA-19449
URL: https://issues.apache.org/jira/browse/CASSANDRA-19449
Project: Cassandra
Issue Type: Bug
Components: Build, Documentation
Reporter: Jon Haddad
We're saying that C* has experimental JDK 17 support yet the 5.0 branch can't
be built with it.
{noformat}
ubuntu@ip-172-31-36-36:/usr/local/cassandra/current$ ant
Buildfile: /usr/local/cassandra/trunk/build.xml
[echo] Non default JDK version used: 17
init:
BUILD FAILED
/usr/local/cassandra/trunk/build.xml:388: Directory
/usr/local/cassandra/trunk/build/classes/main creation was not successful for
an unknown reason
Total time: 1 second
ubuntu@ip-172-31-36-36:/usr/local/cassandra/current$ java -version
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment (build 17.0.10+7-Ubuntu-122.04.1)
OpenJDK 64-Bit Server VM (build 17.0.10+7-Ubuntu-122.04.1, mixed mode, sharing)
{noformat}
Trying to use a similar flag to -Duse.jdk11=true fails as well:
{noformat}
ubuntu@ip-172-31-36-36:/usr/local/cassandra/current$ ant -Duse.jdk17=true
Buildfile: /usr/local/cassandra/trunk/build.xml
[echo] Non default JDK version used: 17init:BUILD FAILED
/usr/local/cassandra/trunk/build.xml:388: Directory
/usr/local/cassandra/trunk/build/classes/main creation was not successful for
an unknown reasonTotal time: 0 seconds{noformat}
I see this in build.xml:
{noformat}
<property name="java.supported" value="11,17" />{noformat}
I think a bigger picture question is, why do we require special flags to build
different JVM versions? Is this a limitation of ant, or the way we've
configured it?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
