Today we released version 0.7.0 of the obfuscate4e feature.

This version adds automatic detection (and exclusion from obfuscation) of classes used in the plugin’s extensions. This feature requires Eclipse 3.4 (or above) to work correctly. We also included an Obfuscate4e section for Eclipse’s online help.

We just released version 0.6.3 of obfuscate4e plugin. This version fixes a bug introduced in version 0.6.2.

This release is avaliable at the download section at sourceforge.net as well as via the update site.

There is a critical bug in version 0.6.2 which leads to a lot of false library entries. This slows down the obfuscation process tremendously and may lead to failure.

A fixed version will be available shortly. For now, please, don’t update to version 0.6.2.

Sorry for the trouble.

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 have custombuildcallbacks.xml generated, yes? It’s not as simple as just doing this of the main plugin with the product definition, is it?

We used the christmas holidays to work on obfuscate4e a bit. So it’s time for a new release!

This version features: