You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/07/09 16:17:00 UTC
[jira] [Commented] (CASSANDRA-14562) JNA 4.4.0 pulled in when using
cassandra-all from libraries
[ https://issues.apache.org/jira/browse/CASSANDRA-14562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537166#comment-16537166 ]
ASF GitHub Bot commented on CASSANDRA-14562:
--------------------------------------------
GitHub user JeetKunDoug opened a pull request:
https://github.com/apache/cassandra/pull/240
[CASSANDRA-14562] Exclude JNA from Chronicle's dependencies to avoid …
…bringing 4.4.0 into consumers of Cassandra as a library
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/JeetKunDoug/cassandra CASSANDRA-14562-fix-jna-dependency
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cassandra/pull/240.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #240
----
commit 34d5719ac33826e90e952d92e5204247c611e08f
Author: Doug Rohrer <dr...@...>
Date: 2018-07-09T15:51:11Z
[CASSANDRA-14562] Exclude JNA from Chronicle's dependencies to avoid bringing 4.4.0 into consumers of Cassandra as a library
----
> 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: Libraries
> Reporter: Doug Rohrer
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org