[
https://issues.apache.org/jira/browse/CASSANDRA-18106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699009#comment-17699009
]
Brandon Williams commented on CASSANDRA-18106:
----------------------------------------------
And finally here is trunk with what was CASSANDRA-18293 rebased and applied (no
more JAVAx_HOME):
||Branch||CI||
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18106-trunk]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/908/workflows/6f8013a1-041e-4ed2-a82b-99512eba806f],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/908/workflows/a858c49d-9647-4bf6-940d-9b8b154ebe18]|
> 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: 5.x
>
> Attachments: Screenshot 2023-03-03 at 09.24.50.png
>
>
> 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]
