Note: There's an obvious binary search solution to the problem here, but I wonder if anyone has a shortcut.
I have a working test of some code that launches a fairly complex collection of services in Felix 5.6.1. Then, I tried to port across a more sophisticated test. I changed nothing about what goes into the container. However, I added quite a bit to the container's classpath. Result: One part of 'jetty' gets a class not found exception on another. Both pieces are in active bundles, and, again, all this works just fine in the simple version. So, I reason, some jar file on the large list of dependencies I added to the test's classpath contains some package that is on the long list of Export-Package packages that end up on the system bundle by default. Absent some shortcut, I'll binary search adding dependencies from good to bad until I find the culprit. I'm not sure why I think that there could be royal road to this, but perhaps someone's been here. _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
