[
https://issues.apache.org/jira/browse/CASSANDRA-18179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17679641#comment-17679641
]
Michael Semb Wever commented on CASSANDRA-18179:
------------------------------------------------
bq. I just read through the patch again and I still think we need to update CCM
in parallel as it considers CASSANDRA_USE_JDK11 here
CASSANDRA_USE_JDK11 can still be set in this situation. It's the build scripts
that will remove the setting of that flag, not this build.xml patch.
What will break is where scripts/tools grep the build.xml for
CASSANDRA_USE_JDK11 as a way to detect if jdk11 is possible. Does ccm do that
anywhere?
> 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
