[
https://issues.apache.org/jira/browse/CASSANDRA-17951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748668#comment-17748668
]
Stefan Miklosovic commented on CASSANDRA-17951:
-----------------------------------------------
I noticed that in cassandra-4.1 branch we have this (1). In trunk, the way how
we specify dependencies have changed to Maven poms and this was lost in
translation.
I have aligned junit bom in the patch to 5.9.1 as advised.
To be on the safe side of things I will do one more run.
(1) https://github.com/apache/cassandra/blob/cassandra-4.1/build.xml#L699-L703
(2)
https://github.com/apache/cassandra/pull/2511/commits/a43d738f008f2d07c75d113d505524ac1b38a8d9
> Update AssertJ
> --------------
>
> Key: CASSANDRA-17951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17951
> Project: Cassandra
> Issue Type: Task
> Components: Dependencies
> Reporter: Ekaterina Dimitrova
> Assignee: shylaja kokoori
> Priority: Normal
> Fix For: 5.x
>
> Attachments: 17951.patch, 17951_1.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> From the changelog of AssertJ
> [here,|https://assertj.github.io/doc/#assertj-core-3-23-1-release-notes] it
> seems JDK17 is tested and relevant issues fixed as per 3.23.1, and we are on
> 3.15.0
> This ticket should accommodate an upgrade to the latest version of AssertJ
> for trunk.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
