1#
2# This ProGuard configuration file illustrates how to process the ProGuard GUI.
3# Configuration files for typical applications will be very similar.
4# Usage:
5#     java -jar proguard.jar @proguardgui.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 classes, Gradle classes, and WTK classes, keeping
11# everything else.
12
13-injars  ../lib/proguardgui.jar
14-injars  ../lib/proguard.jar(!META-INF/**,!proguard/ant/**,!proguard/gradle/**,!proguard/wtk/**)
15-injars  ../lib/retrace.jar (!META-INF/**)
16-outjars proguardgui_out.jar
17
18-libraryjars <java.home>/lib/rt.jar
19
20# If we wanted to reuse the previously obfuscated proguard_out.jar, we could
21# perform incremental obfuscation based on its mapping file, and only keep the
22# additional GUI files instead of all files.
23
24#-applymapping proguard.map
25#-injars      ../lib/proguardgui.jar
26#-outjars     proguardgui_out.jar
27#-libraryjars ../lib/proguard.jar(!proguard/ant/**,!proguard/wtk/**)
28#-libraryjars ../lib/retrace.jar
29#-libraryjars <java.home>/lib/rt.jar
30
31
32# Allow methods with the same signature, except for the return type,
33# to get the same obfuscation name.
34
35-overloadaggressively
36
37# Put all obfuscated classes into the nameless root package.
38
39-repackageclasses ''
40
41# Adapt the names of resource files, based on the corresponding obfuscated
42# class names. Notably, in this case, the GUI resource properties file will
43# have to be renamed.
44
45-adaptresourcefilenames **.properties,**.gif,**.jpg
46
47# The entry point: ProGuardGUI and its main method.
48
49-keep public class proguard.gui.ProGuardGUI {
50    public static void main(java.lang.String[]);
51}
52