[jira] [Comment Edited] (CASSANDRA-18106) Update CCM for JDK17 and revise current JDK detection strategy

["Ekaterina Dimitrova (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678871#comment-17678871 ] 

Ekaterina Dimitrova edited comment on CASSANDRA-18106 at 1/19/23 8:33 PM:
--------------------------------------------------------------------------

We do not have CCM component so assigning it to CI. Assigning 4.x for fix version but if we see some issue with the JDK detection we might want to test any patches with the previous Cassandra versions too


was (Author: e.dimitrova):
We do not have CCM component so assigning it to CI.

> Update CCM for JDK17 and revise current JDK detection strategy
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-18106
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18106
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 4.x
>
>
> As part of CASSANDRA-16895 initial POC an initial version of CCM patch was created. This needs to be revisited and reviewed
> Recently we closed CASSANDRA-18039 which brought questions, probably we need to revise how we detect JDK versions in CCM and whether it is correct. To the best of my knowledge there are certain tests in the repo around that and they pass so my guess is we need to revise just the strategy and maybe document it explicitly or consider if we want any changes to be applied. Also, we need to be careful with breaking changes. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org