[ 
https://issues.apache.org/jira/browse/CASSANDRA-17869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645402#comment-17645402
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17869:
-------------------------------------------------

The way I did it so far is only switching the current strategy from JDK11 to 
JDK17 as that was what we discussed when this whole migration to JDK17 
conversation started. So I am not opposed to other ideas but so far I remove in 
trunk {{CASSANDRA_USE_JDK11}} and {{-Duse.jdk11=true and switch to 
}}{{CASSANDRA_USE_JDK17}}{{ and }}{{{}-Duse.jdk17=true{}}}{{{}{}}}

I guess what you are looking for is automated detection of JDK version and 
logging - "you use this version" and "version 7 (for example) is detected, it 
is not supported"? Now while looking into that we realized we do not officially 
test non-LTS versions between 8 and 11 and the same will be between 11 and 17, 
but some people may be testing etc and those are not prohibited for usage at 
the moment. I guess that encourages early testing with new JDKs too. 

Now the big question on my mind is:

Do we keep the old cassandra branches as is with cassandra-builds still in 
place and initiate a change only for trunk (bringing scripts to .build)? Then 
we introduce for trunk that new way of handling things as you suggested? I 
guess we need to come up with exact plan/suggestion around that and bring it to 
the mailing list as it might be disruptive for certain people? (though if it is 
only trunk so far, it should be less disruptive but still awareness needed). 
Does it make sense what I am saying here? 

 

 

> Add JDK17 option to cassandra-builds (build-scripts and jenkins dsl) and on 
> jenkins agents
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17869
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17869
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>
> Add JDK17 option to cassandra-builds build-scripts, they only currently 
> support options {{8}} and {{1}}.
> Add JDK17 to the matrix axes in the jenkins dsl.
> Ensure JDK17 is installed on all the jenkins agents.



--
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

Reply via email to