break? it should produce valid .class files, why would it break? what about shrinking? proguard has different steps for shrinking code, optimizing and obfuscating
On Sun, Mar 8, 2009 at 10:57 PM, thesquib <[email protected]> wrote: > > The optimisation part of proguard will likely break the conversion to > dalvik byte code. Obfuscating will be fine. > > On Mar 9, 4:10 am, tovmeod <[email protected]> wrote: > > I searched the forum and it seems that most question in the area are > > how to put it to work, my question is if it does make any sense to use > > such a tool. > > > > I have some experience with j2me, and with it not only worth it (it > > decreases the final jar size) but it makes sense to obfuscate (company > > didn't want people reversing the code) > > > > so does it? anyone have experience with that? > > any thoughts? > > > > thanks in advance > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---

