Exported packages from embedded jars are not exposed to Eclipse compiler about bndtools HOT 3 CLOSED

Right, I've done some digging, and this doesn't seem all that easy. In BndContainerInitializer, we find calculateEntries which should also include the embeddded jars if they are on the bundle's classpath. Eclipse's IPath doesn't seem to understand paths inside a jar (that is, the "!" notation doesn't work).

How about extracting these jars to a temporary directory? Or is there some way in which we can add single classes (or packages) to the list of classpathentries, so we can work with the declared exports after digging around in the bundle?

from bndtools.

I think on balance it's best not to try to fix this. Embedded JARs are never going to be understood by javac for offline builds, so if I add support for them in Eclipse it will just create inconsistency between the Eclipse and offline builds. Also they create runtime problems in PojoSR.

Best to avoid embedded JARs altogether, or at least use them for private packages only.

from bndtools.

Okay, sounds reasonable. We have now resorted to repackaging the jars we get in, before placing them in our CNF repository (such as, flatten the jar, and include the source or javadoc in OSGI-OPT).

from bndtools.