[
https://issues.apache.org/jira/browse/CASSANDRA-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701303#comment-17701303
]
Michael Semb Wever edited comment on CASSANDRA-18049 at 3/16/23 4:58 PM:
-------------------------------------------------------------------------
Dependency changes (post dev@) are now:
Added (a few of these have been pinned so to specify a more recent version)
* affinity-3.23ea1.jar
* jffi-1.3.11-native.jar
* jffi-1.3.11.jar
* jna-platform-5.13.0.jar
* jnr-a64asm-1.0.0.jar
* jnr-constants-0.10.4.jar
* jnr-ffi-2.2.13.jar
* jnr-x86asm-1.0.2.jar
* posix-2.24ea4.jar
Upgraded
* chronicle-bytes-2.20.111.jar --> chronicle-bytes-2.23.33.jar
* chronicle-core-2.20.126.jar --> chronicle-core-2.23.36.jar
* chronicle-queue-5.20.123.jar --> chronicle-queue-5.23.37.jar
* chronicle-threads-2.20.111.jar --> chronicle-threads-2.23.25.jar
* chronicle-wire-2.20.117.jar --> chronicle-wire-2.23.39.jar
patches:
-
https://github.com/apache/cassandra/compare/trunk...michaelsembwever:cassandra:mck/18049/trunk
-
https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:cassandra-dtest:mck/18049
CI:
- j8+j11:
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/130
- j11+j17:
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/136 (using
CASSANDRA-18247)
(plenty of 17 failures there, but none seem related to this ticket)
was (Author: michaelsembwever):
Dependency changes (post dev@) are now:
Added (a few of these have been pinned so to specify a more recent version)
* affinity-3.23ea1.jar
* jffi-1.3.11-native.jar
* jffi-1.3.11.jar
* jna-platform-5.13.0.jar
* jnr-a64asm-1.0.0.jar
* jnr-constants-0.10.4.jar
* jnr-ffi-2.2.13.jar
* jnr-x86asm-1.0.2.jar
* posix-2.24ea4.jar
Upgraded
* chronicle-bytes-2.20.111.jar --> chronicle-bytes-2.23.33.jar
* chronicle-core-2.20.126.jar --> chronicle-core-2.23.36.jar
* chronicle-queue-5.20.123.jar --> chronicle-queue-5.23.37.jar
* chronicle-threads-2.20.111.jar --> chronicle-threads-2.23.25.jar
* chronicle-wire-2.20.117.jar --> chronicle-wire-2.23.39.jar
patches:
-
https://github.com/apache/cassandra/compare/trunk...michaelsembwever:cassandra:mck/18049/trunk
-
https://github.com/apache/cassandra-dtest/compare/trunk...thelastpickle:cassandra-dtest:mck/18049
CI:
- j8+j11:
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/130
- j11+j17:
https://app.circleci.com/pipelines/github/michaelsembwever/cassandra/136 (using
CASSANDRA-18247)
(plenty of 17 failures there, but none seem related to this ticket)
> 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: [email protected]
For additional commands, e-mail: [email protected]
