If I was adding Proguard for the first time then sure I have to solve the problem. For that one first time for all my prohjects.
If I had already been using Proguard as part of my release process, why would it suddenly mess up my release? Part of a Maven build is to lock down everything using version nrs. So unless I decide to bump the versioon of Proguard I'm using it won't happen. And if I do bump the Proguard version and it causes a failure then 1) I have explicilty chosen to do so 2) I can easily rollback to the old version of Proguard. Release goes out as scheduled. On Sep 23, 11:11 pm, JP <[email protected]> wrote: > On Sep 22, 11:53 pm, William Ferguson <[email protected]> > wrote: > > > But hey, I place higher value than some on those 3 : simple, clear and > > maintainable. > > Nice framework, but I don't see how you're "off the hook". Imagine > you're under time pressure to get a release out and you realize > Proguard messes up your release. Now you have to go and mess with the > settings, hoping you can dial it within a few minutes. -- 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
