[
https://issues.apache.org/jira/browse/CASSANDRA-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755582#comment-17755582
]
Michael Semb Wever commented on CASSANDRA-18688:
------------------------------------------------
What are users asking for? JDKs in between 11 or 17 or only newer above 17 ?
How difficult is it to edit the bin/cassandra script (or cassandra.in.sh) for
them to get what they want ?
What signal (advertently or not) are we giving by providing the `-J` option ?
Would a env var be a better signal ? (I think the use of `-J`, if we accept
it, should still print a loud warning.)
[~skokoori], I'm interested in your opinion here, as you are best
representative of the user here.
How does this impact the other scripts ? I know [~claude] was digging into the
.in.sh scripts, as they are a bit of a mess.
I agree that the scripts should by default fail-fast if a jdk not included in
`java.supported` is used.
> 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
>
> Time Spent: 1h 20m
> 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]
