[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847378#comment-17847378 ] Ariel Weisberg commented on CASSANDRA-19636: I didn't test this yet (still working on getting the existing changes to run), but +1 on what I saw in the PR and its description. > 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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847061#comment-17847061 ] Jacek Lewandowski commented on CASSANDRA-19636: --- [~aweisberg] can I assume that you are ok with this ticket? > 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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846984#comment-17846984 ] Jacek Lewandowski commented on CASSANDRA-19636: --- Yes, this is a separate thing, I'll create a ticket for further cleanups. > 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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846980#comment-17846980 ] Ariel Weisberg commented on CASSANDRA-19636: Great! I assume separately the [upgrade_manifest.py](https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py#L228) to not depend on the JAVAX_HOME so we have a more canonical set of things to test? > 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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846966#comment-17846966 ] Jacek Lewandowski commented on CASSANDRA-19636: --- This reverts my previous changes so in terms of automatic selection of Java version is works mostly as before. {quote} * Allowing specifying JDK version as a parameter and then look up the actual JDK location from JAVAX_HOME {quote} This is implemented > 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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846957#comment-17846957 ] Ariel Weisberg commented on CASSANDRA-19636: In terms of future direction for CCM behavior. If CCM automatically selecting a compatible version goes away we should minimize the number of things you need to manage to make CCM do the thing. * Ignore PATH and only use JAVA_HOME * If JAVA_HOME JDK is incompatible return an error * Allowing specifying JDK version as a parameter and then look up the actual JDK location from JAVAX_HOME Existing users now don't need to modify environment variables to do whatever it is they are trying to do with CCM. > 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
[jira] [Commented] (CASSANDRA-19636) Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
[ https://issues.apache.org/jira/browse/CASSANDRA-19636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846945#comment-17846945 ] Michael Semb Wever commented on CASSANDRA-19636: CI - 5.0 [^CASSANDRA-19636_50_75_ci_summary.html] , [^CASSANDRA-19636_50_75_results_details.tar.xz] - trunk [^CASSANDRA-19636_trunk_76_ci_summary.html] , [^CASSANDRA-19636_trunk_76_results_details.tar.xz] > 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