[
https://issues.apache.org/jira/browse/CASSANDRA-5872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13883950#comment-13883950
]
Sylvain Lebresne commented on CASSANDRA-5872:
---------------------------------------------
bq. Removing <dependency groupId="net.java.dev.jna" artifactId="jna"> from
<artifact:pom id="build-deps-pom" artifactId="cassandra-build-deps"> seems to
get rid of the download. Build succeeds without build.xml containing the
aforementioned dependency, so maybe we want to get rid of it?
I believe the "dependency" in the build.xml are there largely for the sake of
generating a valid pom for maven, which we use when doing releases so things
get pushed to the repository.apache.org first and to maven central later. So I
do think we need to have that dependency even though as long as you're just
building with ant it's definitively not necessary. Why does it still get
downloaded when you do 'ant build' and not only when you do 'ant release', I
don't know and maybe that can be improved, but I believe that's the case
already for every other dependency we bundle, so I'd suggest to just include
the dependency and leave cleaning the build process up to another ticket if we
want to give that a try.
bq. adding jna works on linux (haven't tested windows yet) but cassandra
still needs the -Dcassandra.boot_without_jna=true override to start on OSX
Right, so that means CASSANDRA-6575 is broken for OSX. I've re-open that ticket
for fixing that, but there is no reason to hold this ticket for that, it's
clearly not a problem of the bundling itself.
> 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)
