“ > Given we need to upgrade to support JDK17 it seems fine to me. The only concern I have is that some of those libraries are already pretty old, for example the most recent jna-platform is 5.13.0 and 5.5.0 is almost 4 years old. I think we should we use the most recent versions of all libraries where possible?” +1
On Mon, 13 Mar 2023 at 12:10, Brandon Williams <dri...@gmail.com> wrote: > I know it was just an example but we upgraded JNA to 5.13 in > CASSANDRA-18050 as part of the JDK17 effort, so at least that is taken > care of. > > Kind Regards, > Brandon > > On Mon, Mar 13, 2023 at 10:39 AM Jeremiah D Jordan > <jeremiah.jor...@gmail.com> wrote: > > > > Given we need to upgrade to support JDK17 it seems fine to me. The only > concern I have is that some of those libraries are already pretty old, for > example the most recent jna-platform is 5.13.0 and 5.5.0 is almost 4 years > old. I think we should we use the most recent versions of all libraries > where possible? > > > > > On Mar 13, 2023, at 7:42 AM, Mick Semb Wever <m...@apache.org> wrote: > > > > > > JDK17 requires us to update our chronicle-queue dependency: > CASSANDRA-18049 > > > > > > We use chronicle-queue for both audit logging and fql. > > > > > > This update pulls in a number of new transitive dependencies. > > > > > > affinity-3.23ea1.jar > > > asm-analysis-9.2.jar > > > asm-commons-9.2.jar > > > asm-tree-9.2.jar > > > asm-util-9.2.jar > > > jffi-1.3.9.jar > > > jna-platform-5.5.0.jar > > > jnr-a64asm-1.0.0.jar > > > jnr-constants-0.10.3.jar > > > jnr-ffi-2.2.11.jar > > > jnr-x86asm-1.0.2.jar > > > posix-2.24ea4.jar > > > > > > > > > More info here: > > > > https://issues.apache.org/jira/browse/CASSANDRA-18049?focusedCommentId=17699393&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17699393 > > > > > > > > > Objections? > > >
