Don't bother. While there are obfuscators out there, what do you think it will really do?

If you deliver your bytecode, someone can decompile it. Get used to it.

If you want to protect your source, don't deliver the code, run it as a service.

Obfuscators are weak attempts at DRM, and we all know that every attempt at DRM has failed.

10-15-2008, 02:37 AM

piyu.sha

But what if the software need to run on standalone basis. Should there be any way?

10-15-2008, 02:45 AM

fishtoprecords

Write your code in C or assembly.

You simply can't do it in Java. You can pretend to do it. But its impossible to do it robustly.

10-15-2008, 05:44 PM

georgemc

Why bother? What are you hoping to achieve by obfuscation? Unless you've got some marvellous new algorithm or something to keep protected - in which case your first port of call is get a lawyer - then it's not worth the bother. It won't protect your code from piracy, it will only slow down rather than prevent reverse-engineering of your code, and, most importantly, it does nothing to prevent people stealing your ideas, since they can see what your software actually does, simply by using it!

Yeh, obfuscators apparently have some beneficial side-effects if you're deploying to mobile devices, but code obfuscation itself is rarely necessary, if you actually think about it. Just look at the massive amount of top-quality open-source software available, to see how little other people care about this