Community
Participate
Working Groups
If my plugin has a Dynamic-Import: * in it's manifest file, when I launch my eclipse runtime with the -console option and run a "bundle <bundle-id>" against that bundle it shows all of the packages available on the platform in the Imported packages list.
One correction to the above note, it should have been DynamicImport-Package: * not Dynamic-Import: *. Sorry.
What do you expect to see?
For dynamically imported packages, the expectation is to see only the package wirings for the packages which the bundle loaded at least one class or resource from. There are two situations which cause the Framework to aggressively wire dynamic imports. - When PackageAdmin is used to find bundles which import an exported packaged (ExportedPackage#getImportingBundles). If a bundle dynamically imports the exported package then it is wired to the exported package when getImportingBundles is called. This is the case when using the "bundle" command in the console. - When firing ServiceEvents the Framework checks for package consistency between the bundle which registered the service and the listener bundle. If the listener bundle dynamically imports the package then it gets wired to the exported package during this check. The framework should avoid wiring dynamic imports until the bundle actually loads a class or resource from the dynamically imported package. Both cases above can easily be avoided. The fix for this is simple and should be considered for 3.1.1.
Fixed in HEAD (3.2). Will attach patch for R3_1_maintenance branch.
Created attachment 25624 [details] Proposed fix for 3.1.1 Pascal, please review patch for 3.1.1.
Patch good to go. It has been released in the maintenance stream.
*** Bug 100054 has been marked as a duplicate of this bug. ***
