Home | History | Annotate | Download | only in examples 
      1 #
      2 # This ProGuard configuration file illustrates how to process the ReTrace tool.
      3 # Configuration files for typical applications will be very similar.
      4 # Usage:
      5 #     java -jar proguard.jar @retrace.pro
      6 #
      7 
      8 # Specify the input jars, output jars, and library jars.
      9 # The input jars will be merged in a single output jar.
     10 # We'll filter out the Ant and WTK classes.
     11 
     12 -injars  ../lib/retrace.jar
     13 -injars  ../lib/proguard.jar(!META-INF/MANIFEST.MF,
     14                              !proguard/ant/**,!proguard/wtk/**)
     15 -outjars retrace_out.jar
     16 
     17 -libraryjars <java.home>/lib/rt.jar
     18 
     19 # If we wanted to reuse the previously obfuscated proguard_out.jar, we could
     20 # perform incremental obfuscation based on its mapping file, and only keep the
     21 # additional ReTrace files instead of all files.
     22 
     23 #-applymapping proguard.map
     24 #-outjars      retrace_out.jar(proguard/retrace/**)
     25 
     26 # Allow methods with the same signature, except for the return type,
     27 # to get the same obfuscation name.
     28 
     29 -overloadaggressively
     30 
     31 # Put all obfuscated classes into the nameless root package.
     32 
     33 -repackageclasses ''
     34 
     35 # Allow classes and class members to be made public.
     36 
     37 -allowaccessmodification
     38 
     39 # The entry point: ReTrace and its main method.
     40 
     41 -keep public class proguard.retrace.ReTrace {
     42     public static void main(java.lang.String[]);
     43 }
     44