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

Michael Semb Wever commented on CASSANDRA-18049:
------------------------------------------------

With regards to the use of chronicle-core-2.23.36, while chronicle-core-2.23.37 
itself is available publicly, it's parent pom is not, and uses other 
dependencies that are SNAPSHOTs. So that version (2.23.37) is out for us, and 
are using 2.23.36


bq. The patch seems ready for another CI run.

Only comments have been added to the patch since the last runs (which includes 
circleci jdk17) 🤷🏻‍♀️ 

> Update Chronicle Queue
> ----------------------
>
>                 Key: CASSANDRA-18049
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18049
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Ekaterina Dimitrova
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 5.x
>
>
> According to [this|https://chronicle.software/chronicle-support-java-17] 
> article:
> {code:java}
> Starting from chronicle-bom-2.22ea26, all new releases can be run under Java 
> 17 when run on the class path (but not yet under the module path).{code}
> This BOM is newer than what we currently have in both 4.1 and trunk. 4.1 
> points in comments to 
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/1.16.23] which 
> I believe was just forgotten to be updated/removed. The versions we see 
> correspond to this BOM 
> [https://mvnrepository.com/artifact/net.openhft/chronicle-bom/2.20.226]
> It is still older than chronicle-bom-2.22ea26 so we need to upgrade. I 
> suggest we also add a comment again which BOM is considered, this makes 
> things easier.
> Further to running CI, review of the CHANGE logs needs to happen to ensure we 
> do not miss anything that can impact us and it is not caught by our tests.
> For testing with JDK17, please, contact [~e.dimitrova] for latest branch and 
> CI config (at this point feature branch in the cassandra repo does not exist)
>  



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