[
https://issues.apache.org/jira/browse/MESOS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938268#comment-13938268
]
Vinod Kone commented on MESOS-855:
----------------------------------
commit 5c174df1a9a81e52f6a82b5986b0a337921ed1a8
Author: Till Toenshoff <[email protected]>
Date: Mon Mar 17 12:35:26 2014 -0700
Deprecated use of MESOS_NATIVE_LIBRARY for JVM frameworks.
Introduced a new environment variable, MESOS_NATIVE_JAVA_LIBRARY. That
variable still points towards libmesos. For allowing a smooth
transition away from MESOS_NATIVE_LIBRARY towards
MESOS_NATIVE_JAVA_LIBRARY whithin JVM based frameworks.
Future versions of MESOS_NATIVE_LIBRARY will not point to valid JNI
bindings.
A typical java-based framework relies on mesos.jar to do the loading
but may use some extra logic in its startup to make sure
MESOS_NATIVE[_JAVA]_LIBRARY is set/valid. That extra-logic should now
be adapted by the framework developers to use the new environment
variable instead of the old one. MESOS_NATIVE_LIBRARY is now marked
as being deprecated for use for JVM based frameworks.
Note: MESOS_NATIVE_LIRBRAY will not be removed. It is kept for
frameworks that are not JVM based but need to bind to the
self-contained Mesos library.
Review: https://reviews.apache.org/r/19117
> 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: 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.2#6252)
