[ https://issues.apache.org/jira/browse/CASSANDRA-14562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Semb Wever updated CASSANDRA-14562: ------------------------------------------- Fix Version/s: 4.0-beta1 4.0 > JNA 4.4.0 pulled in when using cassandra-all from libraries > ----------------------------------------------------------- > > Key: CASSANDRA-14562 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14562 > Project: Cassandra > Issue Type: Bug > Components: Dependencies > Reporter: Doug Rohrer > Priority: Normal > Labels: pull-request-available > Fix For: 4.0, 4.0-beta1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In https://issues.apache.org/jira/browse/CASSANDRA-13072, it was decided that > JNA 4.2.2 was the correct version of JNA to pull in given issues with glibc > compatibility. However, when using the `cassandra-all` jar from a library, we > are still pulling JNA 4.4.0 due to the use of the chronicle library (I > believe brought in via the changes in > https://issues.apache.org/jira/browse/CASSANDRA-13983). In order to resolve > this, we should exclude the newer version of JNA from being included in the > generated POM file for the cassandra-all target. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org