[jira] [Commented] (MESOS-855) Move JNI code to separate library

["Tobi Knaup (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836866#comment-13836866 ] 

Tobi Knaup commented on MESOS-855:
----------------------------------

Huge +1

This is an issue on most Linux distros when a users doesn't install the default JDK (very common).
In that case most distros don't put libjvm.so in /usr/lib but /usr/lib/jvm/jdk1.7.0_25_x64/jre/lib/amd64 or similar where we can't find it.
Currently, even if you're just starting a master or slave you'll get "libjvm not found", which is confusing since you're not doing anything with Java.
Pulling the JNI stuff out would solve this.

> Move JNI code to separate library
> ---------------------------------
>
>                 Key: MESOS-855
>                 URL: https://issues.apache.org/jira/browse/MESOS-855
>             Project: Mesos
>          Issue Type: Improvement
>          Components: java api
>    Affects Versions: 0.16.0
>            Reporter: Niklas Quarfot Nielsen
>
> libmesos library dependency to libjvm seems unnecessary for all but for frameworks and executors that use JNI. 
> In order words, it has caused confusion that libjvm is a dependency when people have been writing python or c++ frameworks/executors.
> We could instead build a libmesos-jni which contain the JNI code and which has libmesos as a dependency.



--
This message was sent by Atlassian JIRA
(v6.1#6144)