> actually the problem was caused by various library bundles not having
> included the relevant imports. However, I see a problem there when
> creating library bundles, since you don't know which runtime classes
> that willbe needed of a jar without consulting the source, and the
> error messages on the classloading do not include the current loading
> context (bundle etc). Would it be possible to improve the error
> messages instead having to dig down to debugging the import
> classloader resolving?
> Thanks for the great help anyway!
> On May 5, 2006, at 6:35 PM, BJ Hargrave wrote:
I opened bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=140568
to add better diagnostic messages when classes cannot be