+1
I have a similar need in the near future, related to slight changes needed in the DRMAA API source code to facilitate their usage with OSGi/Eclipse and DS.
(related CQs 12473 and 12474 are ongoing)
I’ve asked advice to Eclipse EMO about how to handle this : either try to get things in Orbit as a whole, or host the minimal source changes in our Eclipse Triquetrum repository…
(and then still try to use Orbit as redistribution facility?)
Regards
erwin
From: orbit-dev-bounces@xxxxxxxxxxx [mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
Sent: Wednesday, May 3, 2017 12:40 PM
To: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Subject: [orbit-dev] Extending the Orbit Scope
Greetings Orbit Committers,
I was wondering if we should extend the Orbit project scope slightly to allow including code that facilitates a better integration of popular libraries with Eclipse.
As an example I published:
It's a small bundle that would provide a binding for SLF4J into the Eclipse Platform log.
