First Obfuscate4e tests on Eclipse 3.5

Submitted by DirkR on Fri, 05/15/2009 - 13:38
in

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.

First of all: It was a joy to use the p2 update manager (don’t flame me to call it an update manager – I know that this is an understatement) to install Obfuscate4e. The installation went well and less any problems. Also the plugin setup worked as expected.

But when I ran the plugin’s build.xml I got an unexpected error message:

post.@dot:
    [proguard] ProGuard, version 4.3
    [proguard] Printing configuration to
             [/home/drue/ws/o4e/mailapp/temp.folder/proguard.cfg]...
      [subant] Failure for target 'post.@dot' of: 
             /home/drue/ws/o4e/mailapp/customBuildCallbacks.xml
      [subant] The following error occurred while executing this line:
      [subant] /home/drue/ws/o4e/mailapp/customBuildCallbacks.xml:37:
             /home/drue/ws/o4e/mailapp/temp.folder/proguard.cfg (No 
             such file or directory)

The ${temp.folder} we used for generated artefacts wasn’t there. I checked the build.xml (generated with Eclipse 3.5) and saw, that this folder is still needed for the PDE build, but does not exist when needed by Obfuscate4e.

So we will test Eclipse 3.5 in more depth and roll out a maintenance release just in time for Galileo.