[
https://issues.apache.org/jira/browse/CASSANDRA-18179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679557#comment-17679557
]
Michael Semb Wever commented on CASSANDRA-18179:
------------------------------------------------
bq. Considering trunk does not yet compile I guess we can just leave a comment
about that in build.xml. And considering that I do not see it a breaking change
that CCM is still not ready as we can't even compile...yet
Yes. the point of the patch's approach is that we can introduce jdk17 now,
regardless of it not yet compiling. This makes it a little easier to coordinate
the changes onwards in other repos.
> Update current trunk build.xml and conf scripts for JDK17
> ---------------------------------------------------------
>
> Key: CASSANDRA-18179
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18179
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 4.x
>
>
> To support JDK17 we need to make changes to build.xml and our scripts. There
> is a preliminary patch which makes a switch from JDK8+JDK11 to JDK11+JDK17
> but it will need a change considering CASSANDRA-18133
> CC [~mck]
--
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
