+Ben Whitehead As the Apache Mesos project, we decided to not have "official" (HTTP) API libraries in the repo (http://github.com/apache/mesos), going forward.
As for mesos-rxjava, I'm not sure of its production readiness. Ben Whitehead (it's maintainer) might be able to shed more light on its status. I don't think Jesos speaks the new HTTP API. On Tue, Aug 23, 2016 at 1:19 PM, Hendrik Haddorp <[email protected]> wrote: > Is there any official Java binding available for that? So far I found > these: > https://github.com/mesosphere/mesos-rxjava > https://github.com/groupon/jesos > > Jesos seems to only be build against Mesos 0.22.0. > Do you know if Mesos RxJava looks very current but also quite different > from the old Java API. Is this going to be the new official Java API, > given that it is from Mesosphere? Any idea if this can handle Mesos > master fail overs like the old one should be able to do? > > On 23/08/16 21:13, Vinod Kone wrote: > > If you are writing a new scheduler, I would highly recommend using the > > new HTTP API instead of the Java bindings. This would eliminate the > > dep on the native library. > > > > If you still want to use the old bindings, the easiest way might be to > > install mesos deb package in your docker image. > > > > On Tue, Aug 23, 2016 at 11:27 AM, Hendrik Haddorp > > <[email protected] <mailto:[email protected]>> wrote: > > > > Hi, > > > > I wrote a Mesos scheduler using the Java bindings, which worked > > great so > > far. Now I would like to run my scheduler as a docker container on > > Marathon. The problem is now that I'm missing the required native > > libraries. What is the best way to install them (in Ubuntu) without > > pulling heaps of other stuff? > > > > Thanks, > > Hendrik > > > > > >
