Hi Colin,
Colin Mack wrote:
>I use retroguard (it's free, yeah!).
>
I use retroguard too.
> 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.
>
I don't seem to have to do this. I find that if you obfuscate the
classes before you jar them up you can preverify no problem, i.e. no
need to jar the classes before obfuscating them since you can run
retroguard on the classes themselves.
To summarise
1. Compile code
2. Obfuscate classes
3. Preverify classes
4. Create Jar
CHEERS> SAM
Received on Wed Dec 18 13:09:39 2002