Details
-
Type:
Sub-task
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.0.0
-
Fix Version/s: 3.0.2
-
Component/s: deployment, osgi
-
Security Level: public (Regular issues)
-
Labels:None
Description
right now the deployer adds packages it can detect as used in a gbean to the Import-Packages. However it never populares Export-Package. This causes problems if the class is actually in the plugin/bundle we are constructing. If a bundle contains a class, if it lists the package in Import-Package, it won't satisfy the constraint itself unless the package is also listed in Export-Package.
So, we need to make the deployer list all the packages contained in the bundle in Export-Package. This might be a challenge in case there are embedded jars and a complicated Bundle-Classpath.
For now the workaround appears to be to move any classes used in gbeans to another bundle rather than packing them in a javaee app.