[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] OSGi Remote Service Admin
- From: Thomas Watson <tjwatson@xxxxxxxxxx>
- Date: Fri, 24 Sep 2010 12:59:12 -0500
- Delivered-to: firstname.lastname@example.org
You may want to ask this question on the rt-pmc list. A large amount of the enterprise OSGi specification implementation work at eclipse is going on in the rt.gemini project. That project has already put the enterprise OSGi companion code through the Eclipse IP process in CQ https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4046. ECF should piggy back off that CQ to use the OSGi packages you are interested in.
Scott Lewis ---09/24/2010 12:22:49 PM---Greetings,
Scott Lewis <slewis@xxxxxxxxxxxxx>
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
09/24/2010 12:22 PM
[equinox-dev] OSGi Remote Service Admin
As planned, the ECF project is approaching completion of an ECF-based
implementation of the remote service admin OSGi 4.2 specification .
For those unfamiliar, the remote service admin spec is part of the OSGi
enterprise spec. As appropriate for our project scope, our intention
is to focus only on implementing the remote service admin spec...i.e. we
have no intention or plans for implementing other parts of the OSGi ee
spec (e.g. blueprint, etc).
The remote service admin specification includes classes...and these
classes are included in the 4.2 osgi.enterprise.jar. How should ECF
proceed WRT the IP clearance for these OSGi classes? Are they included
in some overarching Eclipse Foundation-OSGi relationship? Are they
included in the process that the runtime project has for getting new
versions of (e.g.) the core framework spec classes? If not,
could/should they be?
We would obviously rather not have to through a distinct, ECF-specific
IP process for including these OSGi classes in ECF...especially since we
as a project do not currently have an active representative on the
Enterprise experts group. Also, duplicating work already done by the IP
team is undesirable for obvious reasons.
So...how should we proceed WRT use of these OSGi EE classes for remote
equinox-dev mailing list