[
https://issues.apache.org/jira/browse/CASSANDRA-18258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17693372#comment-17693372
]
Michael Semb Wever commented on CASSANDRA-18258:
------------------------------------------------
bq. do we want people to be able to run experimentally on versions between 11
and 17 even after we remove 8?
No. If folk want to experiment with another jdk then they update java.supported
in build.xml
This brings up a separate point. The purpose of the java.default and
java.supported properties in build.xml is to avoid explicit "8", "11", and "17"
in any other files. For example, when we bump to 17 and XX later on, the only
file we touch is build.xml
I appreciate this is raised a bit late, removing the explicit versions in other
files can happen in separate tickets. 18133 will do it for the test scripts.
> Add test conf for JDK17
> -----------------------
>
> Key: CASSANDRA-18258
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18258
> Project: Cassandra
> Issue Type: Task
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 4.x
>
>
> Post CASSANDRA-18252 and CASSANDRA-18179 we will be able to compile current
> trunk with JDK17 but in order to start Cassandra and test it we will need
> also our conf files updated with some preliminary conf for test purposes.
> This ticket will be used to add those to current trunk
--
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
