在Eclipse中为Android启用ProGuard

ProGuard for Android上的新文档说，要在项目主目录中的default.properties文件中添加一行。但是，在打开此文件时，我在顶部阅读：

# This file is automatically generated by Android Tools. 
# Do not modify this file -- YOUR CHANGES WILL BE ERASED! 

我想念什么吗？

另外，是否有一种方法只能针对Eclipse的生产版本（即，在导出成品时）启用ProGuard？

只是后续操作，因为我正在搜索相同的内容-并且这里的答案已经过时-最近，基本的proguard配置位于sdk目录中-因此您只需要将其放入project.properties中：

proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt

如果要进行特定于项目的修改，请创建一个proguard-project.txt并将其行更改为：

proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt:proguard-project.txt 

Android SDK（r20或更高版本）

请检查project.properties中引用的预定义的proguard.config

proguard.config=${sdk.dir}/tools/proguard/proguard-android.txt

更多信息：http : //proguard.sourceforge.net/manual/examples.html#androidapplication

在Gradle上：

buildTypes {
 release {
            minifyEnabled true
            shrinkResources true
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'

            ...
  }
 }

在这里，您可以检查我不断更新的proguard“默认”文件：https : //medium.com/code-procedure-and-rants/android-my-standard-proguard-ffeceaf65521

Android SDK（R19或更低版本）

您可以将其添加到default.properties。到目前为止，我一直在手动添加，没有任何问题。

如果添加行：

proguard.config=proguard.cfg

如前所述，仅在导出签名的应用程序时使用ProGuard（Android工具=>导出签名的应用程序）

如果您在Android 2.3之前使用SDK启动项目，proguard.cfg则不会创建文件（与default.properties2.3>相似）。

要启用其自动创建功能，只需更新至Android 2.3的SDK，然后使用现有资源（这是您当前拥有的项目的资源）创建一个新项目。

自动地将proguard.cfg填充将被创建。

如果仍然如此，则要手动创建它，它应该包含以下内容：

-dontusemixedcaseclassnames
-dontskipnonpubliclibraryclasses
-dontwarn android.support.**
-verbose

-dontoptimize
-dontpreverify


-keepattributes *Annotation* 
-keep public class * extends android.app.Activity
-keep public class * extends android.app.Application
-keep public class * extends android.app.Service
-keep public class * extends android.content.BroadcastReceiver
-keep public class * extends android.content.ContentProvider
-keep public class com.google.vending.licensing.ILicensingService
-keep public class com.android.vending.licensing.ILicensingService
-keep public class * extends android.support.v4.app.Fragment
-keep public class * extends android.app.Fragment

-keepclasseswithmembernames class * {
    native <methods>;
}

-keepclasseswithmembernames class * {
    public <init>(android.content.Context, android.util.AttributeSet);
}

-keepclasseswithmembernames class * {
    public <init>(android.content.Context, android.util.AttributeSet, int);
}

 -keepclassmembers public class * extends android.view.View {
  void set*(***);
  *** get*();
 }

-keepclassmembers enum * {
    public static **[] values();
    public static ** valueOf(java.lang.String);
}

-keep class * implements android.os.Parcelable {
  public static final android.os.Parcelable$Creator *;
}

-keepclassmembers class **.R$* {
  public static <fields>;
}

我想我已经回答了以上所有问题。

更新：

逐行说明：

#Use 5 step of optimization 
#-optimizationpasses 5

#When not preverifing in a case-insensitive filing system, such as Windows. This tool will unpack your processed jars,(if using windows you should then use):
-dontusemixedcaseclassnames

#Specifies not to ignore non-public library classes. As of version 4.5, this is the default setting
-dontskipnonpubliclibraryclasses

# Optimization is turned off by default. Dex does not like code run
# through the ProGuard optimize and preverify steps (and performs some
# of these optimizations on its own).    
-dontoptimize
-dontpreverify

-dontwarn android.support.**

#Specifies to write out some more information during processing. If the program terminates with an exception, this option will print out the entire stack trace, instead of just the exception message.
-verbose

#The -optimizations option disables some arithmetic simplifications that Dalvik 1.0 and 1.5 can't handle. Note that the Dalvik VM also can't handle aggressive overloading (of static fields).
#To understand or change this check http://proguard.sourceforge.net/index.html#/manual/optimizations.html
#-optimizations !code/simplification/arithmetic,!field/*,!class/merging/*

# Note that if you want to enable optimization, you cannot just
# include optimization flags in your own project configuration file;
# instead you will need to point to the
# "proguard-android-optimize.txt" file instead of this one from your
# project.properties file.

#To repackage classes on a single package
#-repackageclasses ''

#Uncomment if using annotations to keep them.
#-keepattributes *Annotation*

#Keep classes that are referenced on the AndroidManifest
-keep public class * extends android.app.Activity
-keep public class * extends android.app.Application
-keep public class * extends android.app.Service
-keep public class * extends android.content.BroadcastReceiver
-keep public class * extends android.content.ContentProvider
-keep public class * extends android.app.backup.BackupAgentHelper
-keep public class * extends android.preference.Preference
-keep public class com.google.vending.licensing.ILicensingService
-keep public class com.android.vending.licensing.ILicensingService
#Compatibility library 
-keep public class * extends android.support.v4.app.Fragment
-keep public class * extends android.app.Fragment

#To maintain custom components names that are used on layouts XML.
#Uncomment if having any problem with the approach below
#-keep public class custom.components.package.and.name.**

# keep setters in Views so that animations can still work.
# see http://proguard.sourceforge.net/manual/examples.html#beans
 -keepclassmembers public class * extends android.view.View {
  void set*(***);
  *** get*();
}

#To remove debug logs:
-assumenosideeffects class android.util.Log {
    public static *** d(...);
    public static *** v(...);
    public static *** w(...);
}

#To avoid changing names of methods invoked on layout's onClick.
# Uncomment and add specific method names if using onClick on layouts
#-keepclassmembers class * {
# public void onClickButton(android.view.View);
#}

#Maintain java native methods 
-keepclasseswithmembernames class * {
    native <methods>;
}


#To maintain custom components names that are used on layouts XML:
-keep public class * extends android.view.View {
    public <init>(android.content.Context);
}
-keep public class * extends android.view.View {
    public <init>(android.content.Context, android.util.AttributeSet);
}
-keep public class * extends android.view.View {
    public <init>(android.content.Context, android.util.AttributeSet, int);
}

#Maintain enums
-keepclassmembers enum * {
    public static **[] values();
    public static ** valueOf(java.lang.String);
}

#To keep parcelable classes (to serialize - deserialize objects to sent through Intents)
-keep class * implements android.os.Parcelable {
  public static final android.os.Parcelable$Creator *;
}

#Keep the R
-keepclassmembers class **.R$* {
    public static <fields>;
}

###### ADDITIONAL OPTIONS NOT USED NORMALLY

#To keep callback calls. Uncomment if using any
#http://proguard.sourceforge.net/index.html#/manual/examples.html#callback
#-keep class mypackage.MyCallbackClass {
#   void myCallbackMethod(java.lang.String);
#}

#Uncomment if using Serializable 
#-keepclassmembers class * implements java.io.Serializable {
#    private static final java.io.ObjectStreamField[] serialPersistentFields;
#    private void writeObject(java.io.ObjectOutputStream);
#    private void readObject(java.io.ObjectInputStream);
#    java.lang.Object writeReplace();
#    java.lang.Object readResolve();
#}

更新2：

在最新的ADT / Proguard中使用-keepclasseswithmembers代替-keepclasseswithmembernames

至少从ADT 16开始，您确实可以在中添加该行project.properties，并且将保留该行。您可以尝试更改目标SDK版本，并查看project.properties是否已相应更新，但添加的行仍然存在。因此，我认为警告的措词不当；意思是说文件中的设置（例如）target将被项目设置覆盖，反之亦然。

ProGuard配置的更改来自ADT版本17。ProGuard从4.4更新到4.7，并且已经介绍了配置文件参考中的不同之处。请注意，现有项目将保持不变，从而使它们没有此版本和较新的ADT版本中包含的较新规则集。上面的ligi已指出有关较新的配置安排的相关文档，可在以下位置找到：

http://tools.android.com/recent/proguardimprovements “第二，我们更改了配置文件的处理方式。”

您可以将行添加到中build.properties，如中所述default.properties。