O'Reilly logo
  • Tyas Kokasih thinks this is interesting:

Only bundles with a class path entry of . can be used as standard JAR files. Why? The OSGi notion of . on the bundle class path is equivalent to standard JAR file class searching, which is to search from the root of the JAR file as if all relative directories are package names. If a bundle specifies an embedded JAR file or directory, it requires special handling that’s available only in an OSGi environment. Luckily, it isn’t too difficult to avoid using embedded JAR files and directories.

It’s a good idea to try to keep your bundle JAR files compatible with...

From

Cover of OSGi in Action: Creating Modular Applications in Java

Note

OSGi bundles with class path entry of . can be reused as plain JAR file. Albeit losing all of its OSGi-ness.

This classpath entry is specified as:

Bundle-Classpath:

in MANIFEST.MF file