[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691661#comment-17691661
]
Brandon Williams commented on CASSANDRA-18106:
----------------------------------------------
Stripping the '1.8' version down did the trick
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/863/workflows/1dedc810-9884-42d5-9d2c-eb911dcd4495].
bq. Also, trivial, but can we remove the JAVAx_HOME lines (in just trunk):
That's in the templates too, we should probably make another ticket to cleanup
circle. I believe you found the root cause of CASSANDRA-18039 though.
bq. CCM has its own tests and JDK tests also exist
Let me take a look.
> 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]
