- Follow Obfuscate4e on twitter!
- Obfuscate4e moved to Google Code
- Obfuscate4e Summer of Code
- Obfuscate4e uses Trac for project management
- Obfuscate4e's new home is obfuscate4e.org
- Inspect the obfuscated product
- If you upgraded to Obfuscate4e 0.7.1 and want to use Eclipse 3.5 ...
- Version 0.7.1 released
- If you want to replace the embedded proguard lib ...
- First Obfuscate4e tests on Eclipse 3.5
Excluding classes or packages from obfuscation
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 references from plugin extensions (in plugin.xml) are automatically inserted into the obfuscator exclusion list. Thus the obfuscate4e configuration should be updated whenever a new extension is added to the plugin.
Remark: This feature works only on Eclipse 3.4 (there seems to be a bug or non-implemented feature in Eclipse 3.2 and 3.3)
Of course you can add custom exclusion statements by hand. For instance If a class gets instantiated via reflection or is referenced by name in any other way, it has to be excluded.

Recent comments
17 weeks 1 day ago
28 weeks 1 day ago
33 weeks 3 days ago
35 weeks 4 days ago
35 weeks 5 days ago
1 year 3 days ago
1 year 9 weeks ago
1 year 29 weeks ago
1 year 28 weeks ago
1 year 28 weeks ago