[CASSANDRA-19636] Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: NA
• Component/s: Test/dtest/python
• Bug Category: Correctness - Test Failure
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/riptano/ccm/commit/dade9ece5e0199813e180f7915cc342832a2329e

Test and Documentation Plan

automatic ccm tests, manual

• Assignee: Jacek Lewandowski
• Reporter: Jacek Lewandowski

Authors

Jacek Lewandowski

Reviewers

Michael Semb Wever

• Created: 15/May/24 08:50
• Updated: 21/May/24 20:16
• Resolved: 20/May/24 08:35

Description

CCM fails to select the right Java version for Cassandra 5 binary distribution.

There are also two additional changes proposed here:

• add --jvm-version argument to let the user explicitly select Java version when starting a node from command line
• fail if java command is available on the PATH and points to a different Java version than Java distribution defined in JAVA_HOME because there is no obvious way for the user to figure out which one is going to be used

 

Issue Links

• is related to: CASSANDRA-19650 CCM wrongly interprets CASSANDRA_USE_JDK11 for Cassandra 4.x
• relates to: CASSANDRA-18106 Update CCM for JDK17 and revise current JDK detection strategy
• links to: PR