[
https://issues.apache.org/jira/browse/CASSANDRA-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802107#comment-17802107
]
Michael Semb Wever commented on CASSANDRA-18712:
------------------------------------------------
For chronicle-bytes 2.24 the latest early access release is now 2.24ea20
https://repo1.maven.org/maven2/net/openhft/chronicle-bytes/
Are we confident that
- this is stable enough for us? and
- this is compatible with our existing versions of chronicle dependencies we
use ?
https://repo1.maven.org/maven2/net/openhft/chronicle-bytes/2.24ea20/chronicle-bytes-2.24ea20.pom
We need to ensure both stability and compatibility over all chronicle deps.
Can you try bumping the chronicle-bytes version, and seeing how our transitive
dep tree changes ?
All chronicle deps included should only be those we have already declared in
the pom, and match the version numbers as declared. (It is ok to bump other
chronicle versions if we must, but all must be downloadable from repo1.m.o and
no boms must be pulled in.)
> Update Chronicle bytes
> ----------------------
>
> Key: CASSANDRA-18712
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18712
> Project: Cassandra
> Issue Type: Task
> Components: Dependencies
> Reporter: Nayana Thorat
> Priority: Normal
> Fix For: 5.x
>
>
> [https://github.com/OpenHFT/Chronicle-Bytes/pull/485] fixes test failures of
> cassandra on s390x.
> This patch is merged and available in chronicle-bytes-2.24ea7 and later
> releases.
> possible to update Chronicle bytes and related pkg versions in Cassandra
> (https://github.com/apache/cassandra/blob/trunk/.build/parent-pom-template.xml)?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
