[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695906#comment-17695906
]
Michael Semb Wever commented on CASSANDRA-18106:
------------------------------------------------
bq. we are not going to test the upgrade from 4 to 6?
No, because they are not adjacent. We ask users to go through each major
version.
bq. So I guess we consider people are on Java 8 upgrading from 3.11 to 4.1.
Then they switch to 11 and then they upgrade to 5? While we have only JAVA_HOME
how would we have such a complete test? I guess that was the past goal having
those separate JAVAX_HOME, no?
That's two separate tests. The 3.11 to 4.1 upgrade test is found in the
cassandra-4.1 branch (and uses jdk8). Then the 4.1 to 5.0 test is found in the
cassandra-5.0 branch (currently trunk) (and uses jdk11).
> 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
> Assignee: Brandon Williams
> 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: [email protected]
For additional commands, e-mail: [email protected]
