Thanks Richard. I've started work on this. I just want to document one problem with a workaround (should anyone run into the same problem), and then my latest problem.
First problem I encountered almost immediately was with a fragment I have re-exporting extra sun.* internal packages from the system bundle. The issue is registered here https://issues.apache.org/jira/browse/FELIX-2465 but I didn't see my workaround. bindex generated: <require extend='true' filter='(&(symbolicname=system.bundle) For my fragment. I had to change this to: <require extend='true' filter='(&(symbolicname=org.apache.felix.framework) Obviously this ties me to Felix but this is ok for deployment/distribution build. I will also have to do some hacking in the build script to change this string but that's not too hard. Now, my current problem. I use the Jetty OSGi integration to serve up a UI for my app. The Jetty code relies on being able to get the filesystem location for a bundle, I guess because Jetty is still wedded to Files and the filesystem at some level. See bit.ly/KM6pdW [GrepCode link] getBundleInstallLocation(Bundle). The bundle, as provided by OBR, has a location of "obr://[bundle name]/[some string]". Jetty doesn't know how to interpret that. Is there any way of finding the filesystem location from the OBR provided bundle? I realise this isn't very 'OSGi'. Dan
