Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[platform-ui-dev] org.eclipse.osgi dependency

Dear friends of the Eclipse Platform,

I am trying to make the platform independent from the OSGi implementation. Not to get rid of Equinox, but to create options for additional scenarios, e.g. exchanging the SCR/DS implementation or even run an Eclipse RCP app on an embedded device using Concierge.

By trying this I noticed that we have several places where we specify bundle dependencies on org.eclipse.osgi and org.eclipse.osgi.services.

IMHO specifying a bundle dependency on org.eclipse.osgi.services is anyhow wrong. That bundle only includes the OSGi service interfaces. It shouldn't matter from where they are coming from. By trying to exchange Equinox DS with Felix SCR this even results in uses contraint violations.

I created https://bugs.eclipse.org/bugs/show_bug.cgi?id=496557 and provided a patch for this already, which just needs to be merged if nobody has complains.

As next step I wanted to try to remove the bundle dependency to org.eclipse.osgi. But that doesn't seem to be that easy. It starts with org.eclipse.osgi.util.NLS which is surely used quite often.

We could use the E4 translation mechanism at several places, but it won't work in all places (e.g. static classes, Activator and so on) as the E4 translation mechanism is based on OSGi DS.

From a first look I would suggest to move the NLS class in another bundle (e.g. org.eclipse.osgi.util) but I don't know what impact that would have. 

Does anybody have an idea how we can solve this?

Greez,
Dirk

Back to the top