You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2022/12/09 16:43:00 UTC
[jira] [Created] (CASSANDRA-18106) Update CCM for JDK17 and revise current JDK detection strategy
Ekaterina Dimitrova created CASSANDRA-18106:
-----------------------------------------------
Summary: 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
Reporter: Ekaterina Dimitrova
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