It gets broken again if you use the support libraries. Those don't seem to
like proguard-android-optimize.txt and Proguard fails thought it won't with
the proguard-android.txt file used. But the latter will leave the Log
calls in. We need a way to make it work when we use the support libraries.
On Monday, April 23, 2012 12:33:17 PM UTC-7, jtoolsdev wrote:
>
> One of the techniques that I have been using to remove Log messages is to
> use:
>
> -assumenosideeffects class android.util.Log {
> public static int v(...);
> public static int i(...);
> public static int w(...);
> public static int d(...);
> }
>
> This is a very useful way of leaving Log messages intact until you ship.
> So according to the instructions for the new way of using Proguard I put
> the above in the proguard-project.txt file. For some reason it no longer
> removes the calls to Log. To be sure that the proguard-project.txt
> commands got processed I added a line of junk afterwards and indeed
> Proguard stopped on that line issuing an error. So why isn't this working
> any more?
>
>
--
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
