[
https://issues.apache.org/jira/browse/CASSANDRA-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846919#comment-17846919
]
Stefan Miklosovic commented on CASSANDRA-18712:
-----------------------------------------------
I verified that a tarball with this change contains
{code:java}
chronicle-bytes-2.25ea9.jar
chronicle-core-2.25ea13.jar
chronicle-queue-5.25ea13.jar
chronicle-threads-2.25ea6.jar
chronicle-wire-2.25ea12.jar{code}
while the old tarball contains
{code:java}
chronicle-bytes-2.23.33.jar
chronicle-core-2.23.36.jar
chronicle-queue-5.23.37.jar
chronicle-threads-2.23.25.jar
chronicle-wire-2.23.39.jar{code}
There are no changes in libs dir except these.
When it comes to pom.xml (after ant mvn-install), it is same.
> 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
> Assignee: 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
