Obfuscation

It is quite easy to look how obfuscate4e processed your product. You need a de-compiler and an exported Eclipse RCP product. I’ll describe the procedure on a linux box. I use Jode . This Project seems “dead”, at least there were no new ...

Blog entry - DirkR - 06/05/2009 - 14:06 - 0 comments

Today we released version 0.7.1 of the obfuscate4e feature. This version is a maintenance release and closes some Eclipse 3.5 issues as well as minor bugs. Additionally the Eclipse help stuff was separated into it’s own plugin ...

Blog entry - DirkR - 06/03/2009 - 21:05 - 0 comments

You might want to exclude a certain file from obfuscation. This might be the case if the class is used in an extension of your plugin. To exclude a class from obfuscation you have to add a statement like -keep class ...

Book page - DirkR - 01/13/2009 - 22:00 - 0 comments

Obfuscate4e detects exported packages and and writes the corresponding obfuscation exclusion statements automatically into the file proguard.cfg at your plugin’s root directory. Starting from version 0.7 of obfuscate4e all classes ...

Book page - DirkR - 01/13/2009 - 21:34 - 0 comments

Some days ago I received an e-mail related to Obfuscate4e and multi-plugin RCP projects. And as we just got an forum entry with the same topic I will publish the e-mails here. Also, for RCPs built from multiple plugins, each plugin needs to ...

Blog entry - DirkR - 01/08/2009 - 22:03 - 1 comment

It might happen that the obfuscation does not work as expected. In this case there may be some "strange" folders in your project and the generated plugin jar contains non-obfuscated classes. But the build process runs in headless ...

Book page - volker - 02/18/2008 - 14:31 - 0 comments

This screencast demonstrates how to watch the Proguard task working and find out if something went wrong during obfuscation. Very nice presentation Thank you very much for this helpful screencast! May I ask you which Tool you used to ...

Blog entry - DirkR - 01/08/2008 - 10:28 - 3 comments