I'm not familiar with using JBlender to shrink .jar files, so I can't
speak to that.
Most people's first step is to use a Java obfuscator. Are you doing
that yet?
If not I recommend you get one and use it. Obfuscators rename all your
classes, methods & members to 1 or 2 character names so people can't
easily reverse engineer your java programs, but this also has the happy
side effect of reducing the size of your classes, since those names are
all stored in the class files.
I use retroguard (it's free, yeah!). It is a bit of a pain to use,
because retroguard works on completed .jar files, which in turn wrecks
your preverification, which was done on the individual classes before
making the .jar file. So you need to compile, jar the classes, run
retroguard on the jar, split the jar back into classes, preverify the
classes again, make a new jar with the preverified classes. Kind of a
pain but once you put it in a batch file you can just forget about it.
It shrinks the size down a lot for me, but I tend to use super long
variable names because I am old and forgetful :) If you name all your
variables a, b, x, y, etc., it may not do much for you.
There are lots of other things you can do, depending on how desperate
you are :)
- Colin
On 2002.12.18, at 06:35 PM, Ma. Kharisma V. Esguerra wrote:
> is there any other optimizing/compression tool for iAppli jar files
> aside
> from JBlender... i tried compressing my iAppli using JBlender but it
> only
> produced non-downloadable jar file. help...
>
>
> -- Binary/unsupported file stripped by Ecartis --
> -- Type: application/ms-tnef
> -- File: winmail.dat
>
>
>
> This mail was sent to address colin@b-factory.co.jp
> Need archives? How to unsubscribe? http://www.appelsiini.net/keitai-l/
>
Received on Wed Dec 18 12:30:44 2002