You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/03/17 20:37:49 UTC

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

     [ https://issues.apache.org/jira/browse/MESOS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-855:
-----------------------------

    Assignee: Till Toenshoff  (was: Vinod Kone)

> 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
>            Assignee: Till Toenshoff
>
> 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.2#6252)