If you want to replace the embedded proguard lib ...

Submitted by DirkR on Mon, 05/25/2009 - 14:43
in

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.

You might want to test the obfuscation of your code using the Proguard beta release. This can be done within 15 minutes!
just check out the proguard plugin from sourceforge and replace the embedded proguard.jar by it’s beta version:

  • Download the Proguard beta release from sourceforge.net: https://sourceforge.net/projects/proguard/files/ and extract the file lib/proguard.jar
  • Put the lib/proguard.jar file into the the lib/ folder of the proguard plugin, append the version number to the library file name proguard-<version>.jar
  • Adjust the version number of the plugin in the Plugin manifest and in the plugin.xml file to correspond with the version of the proguard release
  • Adjust the exports list for the binary build to include the beta version of the proguard jar instead of the stable version
  • Export the plugin via File > Export > Deployable plugins and fragments
  • Put the exported plugin jar into the plugins folder of your Eclipse instance.

In my case — I replaced proguard-4.3 by proguard-4.4beta3 — I had to

  • download proguard4.4beta3.zip from http://sourceforge.net
  • put the file lib/proguard.jar@ into the proguard plugin’s lib/ folder and rename it to proguard-4.4beta3.jar
  • Change the version number of the proguard plugin to 4.4.0.200905190005b3
  • Change the value of the library attribute to lib/proguard-4.4b3.jar in the plugin.xml file
  • Change the value of the bin.excludes property to lib/proguard-4.4b3.jar in the build.properties file
  • Put the exported file proguard_4.4.0.200905190005b3.jar into Eclipse’s plugins folder.

Remark: Please don’t commit an adopted proguard plugin into the official obfuscate4e subversion repository. The best way to prevent this is to disconnect the plugin from the repository via the plugin’s context menu Team > Disconnect.