I agree that from the description in his post, it is not really clear that it gets him "off the hook" at all. But perhaps he was assuming the reader knows something about maven.
But I am more concerned about his step 3, which sounds like a recipe for trouble: copying the build. Now how do you maintain all the copies and keep them in sync? Or if they are not in sync, how do you keep each one of them up to date with whatever peculiar needs they have? It sounds suspiciously like keeping the same information in more than one place, a classic no-no. On Sep 23, 6:11 am, JP <joachim.pfeif...@gmail.com> wrote: > On Sep 22, 11:53 pm, William Ferguson <william.ferguson...@gmail.com> > 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
