Obfuscate4e moved to Google Code

We just moved the Obfusctate4e project from Sourceforge to Google Code.

There are several reasons to do this:

  • Working against Sourceforge SVN is very slow,
    • Any action on Sourceforge is slow,
  • The project Trac (recently introduced by Sourceforge) never got working because of lacking XMLRPC integration an the legacy ticket system was quite unusable,
  • It took so much time to administer the project.
  • Sourceforge is so slow.

It took me about 2 hours to migrate the project codebase1 and all tickets2 to Google Code AND to integrate the new project into Eclipse Mylyn AND to write this blog post. All it took was to read http://alblue.blogspot.com/2009/04/google-code-and-mylyn-redux.html and process the list step by step.

1 svn export from the old repository, svn checkout of the new repository, copying the folders, and svn ci insside the new checked out workspace. 15 minutes work and finished.

2 Copy and paste of two open tickets ;-)

Comments

New Version?

I see that it has been several months since the last version of Obfuscate4e was released (June 3, 2009).
I believe that version includes Proguard 4.3.0.
The current Proguard release is 4.4, and a Version 4.5Beta2 is also available.
I would like to know if a new version of Obfuscate4e is planned which includes either of these Proguard versions.
Proguard 4.3 had a serious bug which required a somewhat complicated workaround, and an updated version of Obfuscare4e would save us some rework.
Thank you.

Yes, we have the next release almost ready for release

Yes, we have the next release almost ready for release. There are two things to be done: Further testing (I want to test obfuscate4e on a real-world example from other developers) and update of documentation.

But you can test the new version, the (in-official) Update site is located at http://obfuscate4e.org/updates/dev/. It contains Proguard 4.4 and a lot of other improvements. look at the previous blog post Obfuscate4e Summer of Code, it provides some more details on this.

It would be very helpfull, if you can test the new release candidate and provide feedback :)

Best regards
Dirk