- 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
Solving problems
If the obfuscate4e plugin does not work as expected, then you have some possibilities at hand.
- If the obfuscation works manually at first run, but not at subsequent runs: Refresh the Eclipse workspace and check if there is a folder @dot or temp.folder in the plugin project. If they are, then remove it. Eclipse PDE build doesn’t run the customBuildCallbacks if they exist.
- Check the obfuscation setting in the proguard.cfg file in your plugin project. The syntax of this file is explained at the Proguard website (look at the Usage section).
- Run the obfuscation in verbose mode. Ant produces some output which might show the problem.
- Go to the bug tracker, there might be solutions matching your problem.
- If you encountered a bug, then you might submit a bug report.
Please submit the following information:
- The version of your Java and Eclipse installations,
- The contents of proguard.cfg and temp.folder/proguard.map, if available,
- The output of the verbose mode Ant run (see next section for details),
- optionally the MANIFEST.MF of the plugin (to ease the check of the proguard configuration).

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