Hello, I've run into an interesting situation today. I've started using proguard to remove unused methods (no obfuscation/optimization). It works fine for the app, but some of my tests no longer work because methods they need have been removed.
I've figured out the problem is because proguard runs in two steps: first it proguards the app, then it proguards the tests. As a result, things which the app *didn't* need get removed before the test code can show that it *does* need them. In the interim I've just told proguard to not remove the offending methods, but it'd be a lot easier if it'd just proguard the entire app + test at the same time. -Dan -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
