Community
Participate
Working Groups
Created attachment 141160 [details] sample bundles to reproduce the problem If a bundle imports dynamically packages, which are not provided by any other bundle currently installed, the diag command returns the dynamically imported packages as unresolved direct constraints. This really does not affect the resolving of the bundle and it gets resolved correctly and activated, but the imports are still reported by diag. When another bundle providing these packages is installed and activated, diag stops returning the dynamically imported packages as missing for the first bundle. Since diag should return only info why a bundle cannot resolve, it should not report the dynamic imports, because they do not prevent the bundle from resolving. A am attaching two sample bundles to reproduce the bug. Bundle HelloWorldDummy exports the packages com.foo.bar and com.acme.bar, and bundle HelloWorld imports them dynamically. To reproduce the issue follow the steps below: 1. Install HelloWorld 2. Start HelloWorld 3. Run ss command and observe that the bundle status is ACTIVE 3. Run diag command for this bundle 4. Observe that the command reports com.foo.bar and com.acme.bar as unresolved direct constraints 5. Install and run HelloWorldDummy 6. Run diag command for bundle HelloWorld 7. Obsorve that diag reports that there are no unresolved constraints
Created attachment 144075 [details] Patch adding optional/dynamic to unresolved optional/dynamic packages This patch adds to the missing import package, returned by diag, <optional> or <dynamic>, if the import has the respective resolution directive.
Created attachment 144721 [details] patch I decided to use the same approach as the message for optional require-bundle constraints.
Patch released. Thanks Lazar.
Sorry for the spam, forgot to set to FIXED.
