Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 388319

Summary:	Make core.databinding independent of Equinox
Product:	[Eclipse Project] Platform	Reporter:	Ralf Sternberg <rsternberg>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	mknauer, nobody, pascal, pwebster
Version:	4.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Ralf Sternberg

2012-08-29 07:19:56 EDT

The core.databinding framework is designed to be independent from SWT and usable with any UI- or even non-UI toolkit. It would be great if this framework could also be used in other OSGi environments such as Apache Felix.

This is currently not possible because the core.runtime package, which is needed and exposed by core.databinding, is exported by the equinox.common bundle which in turn depends on equinox.osgi.

In a current project, we've created a compatibility bundle to work around this problem. This bundle exports the equinox.osgi packages that are needed by equinox.common. The bundle is currently hosted in the RAP Incubator repository. I've described the problem and our workaround in a blog post [1].

It would be great if the platform could provide a core bundle that exports at least common parts of the core.runtime package and does not depend on Equinox. This would also help to run RAP with JFace on Felix (bug 385033) and probably also for EMF (bug 328227).

[1] http://eclipsesource.com/blogs/2012/08/29/using-eclipse-databinding-with-felix/

Comment 1 Pascal Rapicault

2012-08-29 07:50:46 EDT

Did you try using the org.eclipse.equinox.supplement bundle?

Comment 2 Ralf Sternberg

2012-08-29 09:51:02 EDT

(In reply to comment #1)
> Did you try using the org.eclipse.equinox.supplement bundle?

No, because I didn't know about it :( In fact, this bundle is almost exactly what I was asking for. Thanks.

However, after this ignorance caused me a lot of unnecessary work, I wonder if the situation could be improved to make it easier for others to find the right pieces.

It's not obvious that in order to get the eclipse.core.runtime package, equinox.common and equinox.supplement have to be included. I guess the structure is as it is for historical and compatibility reasons. But wouldn't it be an improvement if there was one org.eclipse.core bundle that exports the core.runtime bits without depending on equinox, and those bits that do require equinox were moved into a separate bundle?

Are there any plans in this direction?

Comment 3 Lars Vogel

2019-11-27 07:32:22 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.