[
https://issues.apache.org/jira/browse/CASSANDRA-18831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17944442#comment-17944442
]
Josh McKenzie commented on CASSANDRA-18831:
-------------------------------------------
Actively on this now. My plan is to:
# Get internal CI to support JDK21 (should be small effort)
# Iron out test failures in that env (using all upstream ASF ccm / dtest /
branch on this ticket code)
# Then move to confirming things are behaving in ASF env
I think retaining the optionality of running everything in 11, 17, and 21 on
trunk until we have this fully ironed out and merged is the right way to go,
much like you did in that ccm patch [~mck]
> JDK21 support
> -------------
>
> Key: CASSANDRA-18831
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18831
> Project: Apache Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Achilles Benetopoulos
> Assignee: Josh McKenzie
> Priority: Normal
> Labels: pull-request-available
> Fix For: 5.x
>
> Attachments: jdk21-patch
>
>
> This patch builds on the work in CASSANDRA-16895 that added JDK17 to the list
> of supported Java versions, and extends that work to enable building and
> running Cassandra under JDK21.
> The following commits comprise the changes included in the attached patch:
> -
> [https://github.com/apache/cassandra/commit/b15d4d6980e787ab5f3405ca8cb17a9c92a4aa47]
> -
> [https://github.com/apache/cassandra/commit/0c5df38dafe58bfec8924e81507bb604e1543897]
> -
> [https://github.com/apache/cassandra/commit/6506b7279d98eed4b2b65b71e0c6f41eb78c6913]
> -
> [https://github.com/apache/cassandra/commit/564cbd534c5a975cda0c629c14c68c8745b41451]
--
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
