[news.eclipse.technology.equinox] Re: Resolving Ambiguity for Import-Pac

[goetz.jexam@xxxxxxxxx (Sebastian Götz)]

Thanks for your answer. Unfortunately it doesn't work for my purpose.
I've got 3 bundles: A, B and C.

I have a framework in two versions. The newer version is encapsulated by 
bundle C. Bundle B consists of adapters, which provide the same structure 
as the older version of the framework. These adapters shall point to their 
corresponding classes in bundle C.
Bundle A contains a client application written against the old version of 
the framework and hence shall link against Bundle B. So the configuration 
looks like this: A->B->C. 
The problem is, that some classes in B and C have the same fully qualified 
name, A shall use B's version of those classes and B shall use C's version 
of these classes.
If i export the classes in C using some version number, import them into B 
and export B's classes for import into A, than A will see C's classes and 
not B's. For me it looks like the import version 2+export version 1 in 
bundle B propagates version 2, because those classes defined in B are 
overwritten by the imported ones.

Is there any solution for this ?
If not, which project should I take as a starting point to enhance the 
current equinox implementation in order to provide a solution for this 
problem?