Niclas Hedhman wrote:
And I am still stunned by the statement that the framework will not deliver q-1.0 to my BundleC if the exporter of q-1.0 imports q, which is resolved to q-1.1 exported by someone else... Can't find it in the spec to neither confirm nor contardict it either, and Richard's reply is also vague on the point...
Standard imports cannot be split, thus if a bundle both imports/exports a given package and import is selected at resolve time (i.e., the bundle ends up importing it from another bundle rather than using its own), then it is not possible for it to ask its fragment for a class in that package, since it will error after asking the exporter it is wired to if the class is not found in the exported package.
-> richard
