Community
Participate
Working Groups
This may be a device kit bug, or possibly just an artifact of older device kit bundles, but a number of our stepstone device bundles do not work with the 3.3.0 org.eclipse.osgi bundle. The problem is masked in eclipse by the fact the necessary classes are available through usage of the "Automated Management of Dependencies" section of the manifest. In order to reproduce, take a device bundle (such as org.eclipse.soda.stepstone.dev.qk145.device.bundle) and remove the entries from the Automated Management of Dependencies section. This results in the following compile error: "The type org.eclipse.soda.dk.device.TransportDevice cannot be resolved. It is indirectly referenced from required .class files org.eclipse.soda.stepstone.dev.qk145.device.bundle/src/org/eclipse/soda/stepstone/dev/qk145/device/bundle QK145DeviceBundle.java line 140 1205264509359 12596" PDE does not automattically add these packages for you (not sure why) and these errors show up in a standalone equinox runtime as NoClassDefFound errors.
We may be able to pull out all the *.bundle imports as well.
Created attachment 92219 [details] QK145 Manifest Patch This patch removes the Automated Management of Dependencies entries and adds the required package imports
Created attachment 92220 [details] mylyn/context/zip
Created attachment 93298 [details] A and D Omni Bundle Patch
we should see if this bug is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=73957 at some point
*** This bug has been marked as a duplicate of bug 73957 ***