I agree with Hal ... obfuscating seems not very useful nowadays.
That said, OSGi does give you the guarantee that not-exported classes
are private and could be obfuscated (as long as you do not have
external references like Spring of course). And well designed bundles
should only export very few packages.
Kind regards,
Peter Kriens
On 15 jul 2009, at 02:58, Scott Selvia wrote:
I'm trying to find information regarding obfuscation and osgi
bundles. From what I have read it seems that:
1. Obfuscation breaks an osgi bundle since the packages are renamed
and the manifest entries don't match.
2. Then another option is to not rename the package names
3. Finally, create a library jar that is obfuscated and then create
an osgi bundle that uses the obfuscated jar.
The first item I can understand, the second item I've read works but
kind of defeats the purpose of obfuscation. The third item I did
not think would work, since the library jar would not have the osgi
bundle entries in the manifest and then could not be loaded via the
osgi framework. The library could be part of the classpath used
when starting the framework but then that takes the flexibility out
of the picture.
So is there an option to obfuscate an osgi bundle? Any white
papers, how-to's, etc... would be appreciated
Thanks
_________________________________________________________________
Windows Live™: Keep your life in sync.
http://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
