[
https://issues.apache.org/jira/browse/CASSANDRA-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704356#comment-17704356
]
Ekaterina Dimitrova edited comment on CASSANDRA-18049 at 3/23/23 8:51 PM:
--------------------------------------------------------------------------
bq. affinity-3.23ea1 is pulling it in.
How do you know that?
affinity-3.23ea1 was initially excluded from chronicle-thread but this patch
removed the exclusion.
When I get it back and I verify that afinity is not pulled anymore with ant
jar, I still see the third-party-bom/3.22.4-SNAPSHOT error pointed by
[~smiklosovic] here. What do I miss?
was (Author: e.dimitrova):
bq. affinity-3.23ea1 is pulling it in.
How do you know that?
affinity-3.23ea1 was initially excluded from chronicle-thread but this patch
removed the exclusion.
When I get it back and I verify that afinity is not pulled anymore with ant
jar, I still see the third-party-bom/3.22.4-SNAPSHOT error pointed by
[~smiklosovic] here.
> 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.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
