- 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
Inspect the obfuscated product
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 releases since 2004. But it works well for this job.
Download the latest jode distribution and extract the file jode*.jar. Then open a shell an go to the folder where you exported the product to. Now execute the command shown below:
java -jar ~/Apps/jode-1.1.2-pre1.jar $(echo plugins/* | tr " " ",")
The $(echo plugins/* | tr " " ",") selects all jars and folders inside the plugins/ directory and compiles tthem into a comma separated list. That’s how jode expects the resources to be inspected.
A window pops up and you can traverse the class structure and look at the obfuscated build.


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