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 and WTK classes.
11
12-injars  ../lib/proguardgui.jar
13-injars  ../lib/proguard.jar(!META-INF/**,!proguard/ant/**,!proguard/wtk/**)
14-injars  ../lib/retrace.jar (!META-INF/**)
15-outjars proguardgui_out.jar
16
17-libraryjars <java.home>/lib/rt.jar
18
19# In recent JREs, some public Swing classes depend on package visible classes,
20# so don't skip these package visible classes while parsing the library jar.
21
22-dontskipnonpubliclibraryclasses
23
24# If we wanted to reuse the previously obfuscated proguard_out.jar, we could
25# perform incremental obfuscation based on its mapping file, and only keep the
26# additional GUI files instead of all files.
27
28#-applymapping proguard.map
29#-injars      ../lib/proguardgui.jar
30#-outjars     proguardgui_out.jar
31#-libraryjars ../lib/proguard.jar(!proguard/ant/**,!proguard/wtk/**)
32#-libraryjars ../lib/retrace.jar
33#-libraryjars <java.home>/lib/rt.jar
34
35
36# Allow methods with the same signature, except for the return type,
37# to get the same obfuscation name.
38
39-overloadaggressively
40
41# Put all obfuscated classes into the nameless root package.
42
43-repackageclasses ''
44
45# Adapt the names of resource files, based on the corresponding obfuscated
46# class names. Notably, in this case, the GUI resource properties file will
47# have to be renamed.
48
49-adaptresourcefilenames **.properties,**.gif,**.jpg
50
51# The entry point: ProGuardGUI and its main method.
52
53-keep public class proguard.gui.ProGuardGUI {
54    public static void main(java.lang.String[]);
55}
56