On Mon, Dec 19, 2011 at 9:54 AM, Nathan <[email protected]> wrote:
> With the latest tools I get this for an Android Library Project: > > Obsolete proguard file; use -keepclasseswithmembers instead of - > keepclasseswithmembernames proguard.cfg > > (I really hope there was more than a cosmetic reason to change this. ) > No, it wasn't cosmetic - there was an error in the default proguard file we used to ship with, which meant that Proguard could strip too much. More details in http:// http://code.google.com/p/android/issues/detail?id=16384 . > > A reasonable person thinks this will go away after I change the - > keepclasseswithmembernames to -keepclasseswithmembers. > > I've done that. I still get the error every time. > Every time you what -- export APK? Or run lint manually? If the issue is that this is aborting your Export APK operation, then you can turn off the automatic error check as part of APK -- there should have been an error dialog popping up telling you exactly how to do that. In any case, go to the Options dialog, under Android find the Lint category and uncheck the checkboxes at the top of that panel. You can also locate the Proguard error below and either change its severity from Error to Warning or even Ignore. Both of these should make the complaint go away. However, I'm still curious as to why the error is triggering for you if you've really fixed the problem. Since you're talking about projects (plural), is it possible that there's still one of the projects that contain the old bad pattern? It's possible that lint is associating the wrong path/project with the error so check all of them. Also, if you're using library projects, the ADT 16 version of lint isn't really library project aware so it's only checking the main project. I've cleaned the projects. I've refreshed. I've restarted Eclipse. > > The error still comes up. > > I click on the proguard.cfg file, which has a red x on it. It comes up > in an editor. It does not have the keepclasseswithmembernames. > > How do I get the changes to "take"? This is getting ridiculous. > Hopefully the above instructions will help make the error go away to unblock you, but I'd be really interested in instructions for how to reproduce this problem, e.g. if your sources are available publicly anywhere (code.google.com or github etc) I can take a look - or even attach something to a new bug at b.android.com . -- Tor -- 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
