java-dev

Christian,

we always had problems with ProGuard optimization, so we disabled it  
anyway. However, our Software that is obfuscated with ProGuard 4.3  
seems to run like it did before the update 4.

Ulli

Am 21.06.2009 um 15:15 schrieb Christian Roth:

> Hello,
>
> this is just a heads-up to anyone using ProGuard <http://
> proguard.sourceforge.net/> to obfuscate and optimize their Java code:
> After installing the latest Java Update 4, my jars created by ProGuard
> seem to be broken.
>
> I was using ProGuard 3.4 for a long time and never had any issues with
> our application. After installing the latest Java update, the jar
> produced by ProGuard started to throw an ArrayIndexOutOfBounds  
> exception
> (when the unprocessed one does not).
>
> I do not know if this is a problem with ProGuard or the Java update at
> this time. I just want to make sure you do a thorough test of your
> ProGuard generated jars built after the Java update to make sure they
> still work, even when you did not change anything else in your  
> configuration.
>
> My workaround for now was to (1) update to ProGuard 4.4beta (4.3 was  
> not
> enough) and (2) disable any optimization routines (running them  
> produces
> an error in ProGuard itself) by specifying -dontoptimize in the  
> ProGuard
> configuration.
>
>
> -Christian
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Java-dev mailing list      ([EMAIL PROTECTED])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/java-dev/kortenkamp%40cinderella.de
>
> This email sent to [EMAIL PROTECTED]

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      ([EMAIL PROTECTED])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/alexiscircle%40gmail.com

This email sent to [EMAIL PROTECTED]