JBOSGI-143 - DynamicImport-Package
Adrian says:
There are three issues here:
1) The dynamic imports are not getting added to the ClassLoadingMetaData requirements (this is because of number 2)
2) The dynamic imports in jboss-cl don't support wildcards
3) Dynamic imports require some kind of lazy resolve handling when the bundle doesn't automatically progess through to ACTIVE.
(1) is trivial except for the handling of (2) which requires a change in jboss-cl. The PackageRequirement only accepts are a single explict package
as it stands.
(3) requires a change to the deployers to implement the Lifecycle api I defined in JBCL-131. JBCL-131 has only remained open becauseI'm not sure its got all the details correct until the deployers implement it and we can test edge cases.
Let me do the next step and create test coverage for
> resolution:=optional
> DynamicImport-Package: org.foo
Wildcard handling can be dealt with in a separate issue. I assigned JBOSGI-143 to myself to do this until FW Alpha4