n order to support dynamic imports, two pieces of functionality need to be added.

1) A fallback local loader which handles all unmatched load requests
2) A way to add dependencies after a module is loaded

This JIRA addresses #2. In the case of dynamic imports, only the import set is modified (not the export set), so adding and recalculating dependencies should just be a question of accepting more AbstractDependencySpecs and then calling Module#resolve() (or a variation which does not cascade to dependencies).

This is complicated in practice by the fact that supporting bundle fragments means adding not only additional dependencies, but also additional resource paths ("they must not have their own class loader though fragments must have their own Protection Domain"), and the exports must cascade to dependencies ("Append the export definitions of a Fragment bundle to the export definitions of the host bundle unless the exact definition (directives and attributes must match) is already present in the host. Fragment bundles can therefore add additional exports for the same package name.").

See OSGi 3.13 for more info.