You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "shylaja kokoori (Jira)" <ji...@apache.org> on 2023/08/09 22:02:00 UTC
[jira] [Updated] (CASSANDRA-18688) Limit Java runtime in 5.0 to JDK17 in scripts; add a flag to opt out of that
[ https://issues.apache.org/jira/browse/CASSANDRA-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
shylaja kokoori updated CASSANDRA-18688:
----------------------------------------
Mentor: Ekaterina Dimitrova
Test and Documentation Plan: Cassandra startup was tested with JDK 8,11, 12, 17 & 19 with and without the -J option
Status: Patch Available (was: Open)
The patch limits startup to JDK11 & 17. I have added an option J to override this behavior
> Limit Java runtime in 5.0 to JDK17 in scripts; add a flag to opt out of that
> ----------------------------------------------------------------------------
>
> Key: CASSANDRA-18688
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18688
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: shylaja kokoori
> Priority: Normal
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, we limit our users from building with non-default Java versions in build.xml.
> They can easily hack build.xml for test purposes with different versions.
> Cassandra–5.0 will be run on JDK11 and JDK17, but on startup, we do not limit people to those two, but only to everything >= 11. We should also put an upper limit of 17 in our Cassandra startup scripts. We can also add a flag to opt-out if someone wants to test with newer versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org