[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846964#comment-17846964 ]
Michael Semb Wever commented on CASSANDRA-19636: ------------------------------------------------ +1 to the patch. we just need CI for (some) <5 branches. > Fix CCM for Cassandra 5.0 and add arg to the command line which let the user > explicitly select JVM > -------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-19636 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19636 > Project: Cassandra > Issue Type: Bug > Components: Test/dtest/python > Reporter: Jacek Lewandowski > Assignee: Jacek Lewandowski > Priority: Normal > Attachments: CASSANDRA-19636_50_75_ci_summary.html, > CASSANDRA-19636_50_75_results_details.tar.xz, > CASSANDRA-19636_trunk_76_ci_summary.html, > CASSANDRA-19636_trunk_76_results_details.tar.xz > > > 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 > -- 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