DirkR's blog

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.

… then you have to re-create the customBuildCallbacks.xml of the plugins too. This is necessary because the PDE build process changed slightly in Eclipse 3.5 and this involves changes in the build script.

You dont need to re-create the Proguard configuration proguard.cfg or change the build.properties. Just press OK in the dialog below and Cancel in the other to submit dialogs.

Today we released version 0.7.1 of the obfuscate4e feature.

This version is a maintenance release and closes some Eclipse 3.5 issues as well as minor bugs. Additionally the Eclipse help stuff was separated into it’s own plugin de.partmaster.obfuscate4e.help.
Obfuscate4e is ready for Eclipse Galileo by now!

The Proguard project provides two distribution versions simultaneously: a stable release (currently version 4.3) and a beta version of the next release (version 4.4 beta 3 actually). Obfuscate4e releases always contain the stable version of Proguard.

I just took Eclipse 3.5M7 and wanted to know if Obfuscate4e (current version 0.7.0) works out of the box with the upcoming release of our favorite IDE. I expected to see it running smoothly.