Xavier stated in another thread that in the next release there will be built-in support for proguard in Eclipse. I can't find a link right now, but the last discussion on it was earlier today or yesterday.
Justin On Thu, Sep 23, 2010 at 8:50 PM, Indicator Veritatis <[email protected]>wrote: > It is not just you. I was pretty disappointed when I read that post, > too. I did get a kick out of seeing what a menacing appearance Dan has > with his new beard and moustache, though;) > > I am amazed that Google seems to think it is acceptable to force the > user to maintain two different build systems -- one for Eclipse and > one for the recommended independent installation of Ant -- and also > maintain a text file with a list of classes not to obfuscate. It is > too obvious that this is a task ADT should be doing. > > But rather than run for the hills, we should pepper Google with > uncomplimentary speculations concerning their motives for this "turd > layering" until they 'fess up and give us a release date for a version > of ADT that will allow us to include Proguard in an Eclipse build > WITHOUT these problems. > > On Sep 22, 9:59 pm, JP <[email protected]> wrote: > > Just read the latest Android Developer blog post. > http://android-developers.blogspot.com/2010/09/proguard-android-and-l... > > Quite the beast. And Proguard cannot even be used with confidence > > ("it’s still possible that in edge cases you’ll end up seeing > > something like a ClassNotFoundException"). > > > > Is it just me getting irritated where this seems to be going? > > In my more active days developing, pretty graphic slang was applies to > > efforts like this: "Turd layering". Meaning: More dependencies, more > > procedure, more sources of error, and it doesn't even work "right". In > > of itself, adding innocent looking steps to a release procedure (for > > some relatively obscure benefit) might be marginally worthwhile, but > > in the bigger picture, releasing an app increasingly becomes a burden. > > Dare you miss a step. Or try to teach somebody else how to go through > > a release and verify it. Or you want to go and rebuild a development > > environment. Or lose the ominous reference file (mapping.txt)... > > > > Anybody care to disagree and convince me this all nice and dandy and > > we don't have to literally run for the hills? > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
