Question

I am trying to obfuscate a bundle with proguard. Because of project specific reasons, my bundles have library jars in them, such as:

bundle.jar
   |
   |-META-INF
   |
   |-library.jar
   |
   \-org (and the rest of my source tree)

The Manifest.mf file in META-INF includes the line:

Bundle-ClassPath: .,library.jar

And this is all auto-generated and good.

Now, the problem comes when proguard tries to obfuscate methods from library.jar (let’s say I have a good reason to do that). In those cases, it won’t find library.jar since it’s not part of the dependent libraries, and proguard seemingly ignores the Bundle-Classpath entry in the manifest file.

So, the question is: can that be done at all? Or is proguard completely osgi agnostic and can’t handle those tags at all? Is there a way I can provide an in-jar dependency to proguard?

Thanks!

Answer 1

Why not assemble the bundle with its embedded JAR after obfuscating with Proguard, rather than before?