On 24 April 2013 19:09, Richard S. Hall <[email protected]> wrote:
> > On 4/24/13 14:05 , David Bosschaert wrote: > >> On 23 April 2013 16:47, Richard S. Hall <[email protected]> wrote: >> >> On 4/23/13 10:54 , David Bosschaert wrote: >>> >>> Forwarding to the Felix mailing list as well. AFAIK, Felix 4.2.1 is a >>>> core >>>> R5 framework. At least it exports the org.osgi.framework in version 1.7 >>>> which tells me it's R5. >>>> >>>> It exports the R5 API, but it doesn't claim to fully implement the R5 >>> API. >>> We moved to the R5 API as a means to make it easier for people to submit >>> patches to implement missing R5 features and to allow us to run the OBR >>> resolver. >>> >>> -> richard >>> >> Is there a list of things that need to be done in order to get to Core R5 >> >> support? Something like a list of JIRAs or something like that? >> This might be useful for people who may want to help out getting there... >> > > Yeah, that would be good. I could look into creating some issues, but if > you want to do it, feel free. > > -> richard > > Let's first see what was introduced in Core R5. After looking at the 4.3/5 specs a little I think the following is new in R5 (I might have missed something though): * New org.osgi.framework.UnfilteredServiceListener interface * New org.osgi.framework.VersionRange class * The Resource API and it's use in the Wiring API * New osgi.identity namespace * New value and new default for org.osgi.framework.bsnversion framework property * support for static valueOf methods in the Filter * Enhanced Bundle.adapt() to support AccessControlContext * Updates to the Bundle Hook Specification (Bundle Collision Hook) Richard maybe you can look at which of the above are supported in Felix and create JIRAs for the missing ones? Cheers, David
