You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2024/01/19 14:13:00 UTC

[jira] [Updated] (CASSANDRA-18688) Limit Java runtime in 5.1 to JDK 11 and 17 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 ]

Ekaterina Dimitrova updated CASSANDRA-18688:
--------------------------------------------
    Summary: Limit Java runtime in 5.1 to JDK 11 and 17 in scripts; add a flag to opt out of that  (was: Limit Java runtime in 5.0 to JDK 11 and 17 in scripts; add a flag to opt out of that)

> Limit Java runtime in 5.1 to JDK 11 and 17 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
>             Fix For: 5.1
>
>          Time Spent: 3.5h
>  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