Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Consider the following use case:
Bundle foo provides package org.foo
Bundle bar wants to import org.foo but also include it in it's bundle classpath such that it can be installed without foo, it should therefore also export org.foo to preserve the classspace should foo and bar be installed in the same jvm
Unfortunately this confuses the sigil resolver which now thinks that bar contains the packages org.foo (as it is exporting them) when at compile time it should pull in bundle foo to satisfy the classes.