[ https://issues.apache.org/jira/browse/CASSANDRA-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804852#comment-17804852 ]
Ekaterina Dimitrova commented on CASSANDRA-18688: ------------------------------------------------- Rebased the branch and squashed the commits here: https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:cassandra:18688-trunk CI is still running here; we need to verify the results when it finishes: https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18688-trunk Please confirm things look good and nothing shifted. I also haven't tested the packaging myself, only local build directly. > 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.0.x, 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