[
https://issues.apache.org/jira/browse/CASSANDRA-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791667#comment-17791667
]
Ekaterina Dimitrova commented on CASSANDRA-18688:
-------------------------------------------------
This ticket is clearly not for a bug; it was filed for trunk, not 5.0.
I would refrain from adding *any* improvements at the last moment 5.0,
especially when there is pressure for a release.
-1 on committing to 5.0
Also, this patch affects packaging (not tested in CircleCI), so we should wait
on CASSANDRA-19083 to test it in Jenkins - at least with JDK11, is it possible?
Thank you [~skokoori] for all your work, diligence, and patience! I will take a
look at the latest code changes later today.
> 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: 2h 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: [email protected]
For additional commands, e-mail: [email protected]
