[
https://issues.apache.org/jira/browse/MESOS-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931628#comment-13931628
]
Till Toenshoff commented on MESOS-855:
--------------------------------------
This approach has been reconsidered and I am now proposing doing a two phase
transition.
Phase 1: Deprecate the old environment variable but leave lib as is.
Phase 2: Split libs as drafted above.
Will suggest another RR for Phase 1.
> 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)
