I believe all frameworks will only make java.* packages automatically available from the JRE, but you can check the org.osgi.framework.system.packages property from the command line to see what yours is doing. If you don't see sun.misc.Unsafe, I think adding it to the org.osgi.framework.system.packages.extra property would work.
On Wed, Sep 30, 2015 at 8:39 PM, Paul F Fraser <[email protected]> wrote: > Hi John, > > Seems that I have a mix of situations. > Some bundles failed because of repository index out of date. > Others because some dependencies were not referenced in the esa file. > > The mapdb bundle requires sun.misc.Unsafe and I think that is the problem > with that subsystem. > > How can I make sun.misc.Unsafe available in a subsystem? > > Thanks > Paul > > > > On 30/09/2015 11:00 PM, John Ross wrote: > > It's too bad that > org.apache.felix.bundlerepository.impl.FelixRequirementAdapter doesn't > override toString or we'd have more to go on. To state the obvious, > something in the co.diderot.mapdb;1.0.1 bundle requires something that is > either not available or visible. Can you identify exactly what requirement > that is and confirm something providing a matching capability is present? > Can you make it work by packaging all of the dependencies of > co.diderot.mapdb;1.0.1 in the subsystem archive rather than relying on the > repository? If you can attach a simple test case reproducing the issue to a > JIRA perhaps we can help more. Questions specifically about Felix OBR > should go to <[email protected]>[email protected] or > [email protected] [1]. > > [1] http://felix.apache.org/mailinglists.html > > On Wed, Sep 30, 2015 at 7:32 AM, Paul F Fraser <[email protected]> > wrote: > >> Hi, >> >> Using very simple subsystem esa files, some of my subsystems install and >> others fail with for example: >> >> org.osgi.service.resolver.ResolutionException: Unable to resolve >> co.diderot.mapdb;1.0.1; >> osgi.bundle: missing requirement >> org.apache.felix.bundlerepository.impl.FelixRequirementAdapter@17a03c1a >> >> The problem is not related to the esa file because I can change the >> Subsystem-Content: to use a bundle that works and all is well. >> >> I have checked the index.xml file in the repository and cannot see any >> difference between bundles that work and those that do not, although I >> could be missing something there. >> >> All of my bundles, the good and the bad are generated using bndtools >> 3.0.0.REL-20150910-120816 the latest from the eclipse market place. >> >> Can anyone suggest what might be causing this problem? >> >> regards >> >> Paul Fraser >> > > >
