Obfuscate4eIntegrates obfuscation into the eclipse PVDF build process. It enables obfuscation of your plugins, features and rcp applications during the regular build.
Obfuscate4eComes withProguardObfuscator, but can easily be adapted for other obfuscators.
You're welcome to join the development team, if you want to improve obfuscate4e or want to integrate additional obfuscators.
Http://obfuscate4e.org/1. Installation of the obfuscate4e feature
To install this feature you simply have to use the Update site facilities built into the Eclipse IDE.
- Inside eclipse goHelp> Software Updates> Find and install...And define a remote site pointing tohttp: // obfuscate4e.org/updates/
2. Configure the obfuscation
Now it's time to configure howObfuscate4eAnd its embedded obfuscator shold work. We use the proguard obfuscator in this sectin. The configuration of other obfuscators will differ.
Execute the actionCreate proguard obfuscation ConfigurationFrom the context menu of the pluginManifest. MF.
In the project folder appear two new files:Custombuildcallbacks. xmlAndProguard. cfg. These files are managed inside your project (and also version controlled ).
Proguard allows to highly customize the obfuscation process. You can add cunfiguration statements toProguard. cfgFile. See
A http://proguard.sourceforge.net/manual/usage.html for valid configuration parameters.
3. obfuscate your code
It's time to use your obfuscator. As it is embedded into the built process eclipse runs the obfuscator when exporting a plugin, a project or a complete product.
Export a pluginFile> export...
The plugin will be obfuscated and exported.
Note: This article Reprinted from: http://obfuscate4e.org/configure-the-obfuscation