[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] target version of osgi specs for juno
- From: Neil Bartlett <njbartlett@xxxxxxxxx>
- Date: Wed, 4 Jul 2012 02:16:00 +0100
- Delivered-to: email@example.com
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>
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.
On 7/3/2012 10:48 AM, BJ Hargrave
Several of the OSGi
in Equinox Juno are used as RI for OSGi Compendium 4.3: DS,
Initial Provisioning, Event Admin, Wire Admin. So all those
are at the Compendium 4.3 level.
I don't know the status of the
OSGi spec impls in Equinox Juno.
ECF  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
Raymond AugÃ Â|ÂSenior Software Architect |ÂLiferay, Inc.Â
equinox-dev mailing list