[
https://issues.apache.org/jira/browse/CASSANDRA-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884800#comment-13884800
]
Lyuben Todorov commented on CASSANDRA-5872:
-------------------------------------------
I removed the last commit from the branch, the jna dependency under
{{artifactId="cassandra-build-deps"}} is again removed. Just cloned a clean
copy of my branch and cleared the maven cache, with the dependency gone, jna
doesn't get downloaded by maven and the build completes successfully.
I think the dependency being removed was part of a group of dependencies, but
jna is already in the main set so having it again doesn't make sense, unless
I'm missing something. From build.xml comments regarding cassandra-build-deps:
bq. each dependency set then defines the subset of the dependencies for that
dependency set
> Bundle JNA
> ----------
>
> Key: CASSANDRA-5872
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5872
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Lyuben Todorov
> Priority: Minor
> Fix For: 2.1
>
> Attachments: 5872-trunk.patch, 5872_debian.patch
>
>
> JNA 4.0 is reported to be dual-licensed LGPL/APL.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
