[
https://issues.apache.org/jira/browse/FELIX-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall updated FELIX-724:
----------------------------------
Description: When searching for a class, we search a bundle's imports, then
required bundles, then content, and finally its dynamic imports. Currently,
dynamic imports are not searched if we have an import for the specific package;
however, we should also not search dynamic imports if the package is visible in
a require-bundle or export as well, otherwise we allow splitting across to an
import, which is not correct. (was: When search for a class, we search a
bundle's imports, then required bundles, then content, and finally its dynamic
imports. Currently, dynamic imports are not search only if we have an import
for the specific package; however, we should also not search dynamic imports if
the package is visible in a require-bundle or export either, otherwise we allow
splitting across to an import, which is not correct.)
> Dynamic imports should not be searched if the bundle already has required or
> exported the package
> -------------------------------------------------------------------------------------------------
>
> Key: FELIX-724
> URL: https://issues.apache.org/jira/browse/FELIX-724
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-1.2.1
> Reporter: Richard S. Hall
> Assignee: Richard S. Hall
> Fix For: felix-1.2.2
>
>
> When searching for a class, we search a bundle's imports, then required
> bundles, then content, and finally its dynamic imports. Currently, dynamic
> imports are not searched if we have an import for the specific package;
> however, we should also not search dynamic imports if the package is visible
> in a require-bundle or export as well, otherwise we allow splitting across to
> an import, which is not correct.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
