[CASSANDRA-14562] JNA 4.4.0 pulled in when using cassandra-all from libraries

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Fix Version/s: 4.0-beta1, 4.0
• Component/s: Dependencies
• Labels: pull-request-available
• Severity: Normal
• Assignee: Unassigned
• Reporter: Doug Rohrer
• Created: 09/Jul/18 14:28
• Updated: 16/Mar/22 13:14
• Resolved: 12/Nov/20 08:18

Description

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.

Issue Links

• duplicates: CASSANDRA-15647 Mismatching dependencies between cassandra dist and cassandra-all pom
• links to: GitHub Pull Request #240
• links to: GitHub Pull Request #240
• links to: GitHub Pull Request #476