+1
Actually, a few month ago I have filed a bug for adding DS to
the Eclipse SDK, see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=253926
Kai
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Chris Aniszczyk
Sent: Montag, 26. Januar 2009 17:35
To: General development mailing list of the Eclipse project.
Cc: Equinox development mailing list
Subject: [equinox-dev] Adding Equinox Declarative Services (DS) to
theEclipse SDK
Howdy y'all. I like to raise the question of us adding
Equinox DS to the Eclipse SDK. DS provides a powerful way to deal with OSGi
services and in my opinion, greatly simplifies the development of services. As
we forge towards Eclipse 3.5, we made a lot of steps to make DS easier to use
in the Eclipse SDK without it actually being in the SDK:
- Prosyst donated a high quality implementation of OSGi DS that made its way to
the Equinox SDK
- PDE release DS component authoring tools as part of a GSOC project and 3.5
work
- The DS spec was updated to work better with lazy bundles (https://bugs.eclipse.org/bugs/show_bug.cgi?id=226575)
Technically, to add DS to the Eclipse SDK all we need to do as add these two
tiny bundles:
org.eclipse.equinox.ds (.15MB)
org.eclipse.equinox.util (.02MB)
So my request in sending this email out is to get the opinion of consumers
(anyone who builds applications on top of Eclipse) and producers (the Eclipse
platform team, especially the Equinox committers). Do consumers see a benefit
of having DS in the SDK? Does the greater Eclipse team feel comfortable with
having DS in the SDK and may use it in the future potentially?
And if we reach a consensus, it would be great to see DS included with the
Eclipse SDK in the 3.5M6 timeframe. If not, at least we had a fun discussion :)
Thoughts?
Cheers,
Chris Aniszczyk
