[
https://issues.apache.org/jira/browse/CASSANDRA-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808403#comment-17808403
]
Michael Semb Wever edited comment on CASSANDRA-18688 at 1/18/24 11:46 PM:
--------------------------------------------------------------------------
bq. do you have your setup working to test the packaging quickly so we can
commit this one?
Yes. Have tested, everything behaves as it should, with debian bullseye, redhat
almalinux, redhat centos7, on jdks 11, 17 and 21.
was (Author: michaelsembwever):
bq. do you have your setup working to test the packaging quickly so we can
commit this one?
Have tested, everything behaves as it should, with debian bullseye, redhat
almalinux, redhat centos7, on jdks 11, 17 and 21.
> Limit Java runtime in 5.0 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.x
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
