[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] target version of osgi specs for juno

Hi Raymond,

That's certainly true for the osgi.core jar, which must be used only as a build-time dependency (and indeed it's better to build against this than against a specific framework such as Equinox, since you avoid accidentally depending on anything not in the spec).

However there is no problem using the osgi.cmpn or osgi.enterprise jars as deployed bundles in the runtime. Some people complain that they are too big and incoherent, but I don't particularly care since they are only interfaces and pure APIs.


On Wed, Jul 4, 2012 at 1:13 AM, Raymond Auge <raymond.auge@xxxxxxxxxxx> wrote:
Thank you for the feedback.Â

The moral of the story is only use the osgi.org API jar's as reference, not as actual deployable artifacts.

- Ray

On Tue, Jul 3, 2012 at 2:27 PM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:
On 7/3/2012 10:48 AM, BJ Hargrave wrote:
Several of the OSGi spec implementations in Equinox Juno are used as RI for OSGi Compendium 4.3: DS, Metatype, Coordinator, Initial Provisioning, Event Admin, Wire Admin. So all those implementations are at the Compendium 4.3 level.

I don't know the status of the other OSGi spec impls in Equinox Juno.

ECF [1] implements Remote Services (compendium in 4.3, core in 5.0) and Remote Services Admin (enterprise) specs.Â

With Juno release, both of these impls are now at the OSGi 5.0 spec level.


[1] http://www.eclipse.org/ecf

equinox-dev mailing list

Raymond Augà Â|ÂSenior Software Architect |ÂLiferay, Inc.Â


8-9 October 2012 |ÂLiferayÂNorth America SymposiumÂ|Âliferay.com/northamerica2012

16-17 October 2012 |ÂLiferayÂEurope SymposiumÂ|Âliferay.com/europe2012

24-25 October 2012 |ÂLiferayÂSpain SymposiumÂ|Âliferay.com/spain2012

equinox-dev mailing list