Lines Matching full:proguard
7 <title>ProGuard Examples</title>
49 <li><a href="#annotated">Using annotations to configure ProGuard</a>
53 directory of the ProGuard distribution.
57 To shrink, optimize, and obfuscate the ProGuard application itself, one would
58 typically create a configuration file <code>proguard.pro</code> and then type:
60 java -jar proguard.jar @proguard.pro
65 -injars proguard.jar
68 -printmapping proguard.map
70 -keep public class proguard.ProGuard {
79 <code>proguard.ProGuard</code> and <code>java.lang.String[]</code>.
106 files</a>. For processing 'simple' applications like ProGuard, that is not
165 unpacks your processed jars, you should then use ProGuard's <a
173 corresponding jad file; ProGuard doesn't do that for you.
193 have java.lang.Class, so we're telling ProGuard not to worry about it.
293 construct. ProGuard will automatically detect them and deal with them, even
294 when their names have been obfuscated. However, older versions of ProGuard and
402 unpacks your processed jars, you should then use ProGuard's <a
413 corresponding jad file; ProGuard doesn't do that for you.
512 as far as ProGuard is concerned.
541 ProGuard doesn't look at your native code, so it won't automatically preserve
724 adapt the execution behavior accordingly. By default, ProGuard treats
756 This option also gets rid of the note that ProGuard prints out about
779 ProGuard first and then invoke the <code>rmic</code> tool. If that is not
1021 This grouping, archiving, and flattening can be arbitrarily complex. ProGuard
1048 Another useful application is speeding up the processing by ProGuard, by
1054 The filter makes ProGuard disregard <code>com.sun.**</code> classes, for
1088 midlets,...) in one go, in order to save time and effort. ProGuard's input and
1092 directories) and a single output directory. ProGuard will then reconstruct the
1108 ProGuard itself, you can still incrementally add other pieces of code that
1109 depend on it, e.g. the ProGuard GUI:
1113 -injars proguard.jar
1116 -applymapping proguard.map
1118 -keep public class proguard.gui.ProGuardGUI {
1126 makes sure the ProGuard part of the code gets the previously produced
1128 ProGuard jar and the additional obfuscated GUI jar.
1143 -libraryjars proguard.jar
1145 -applymapping proguard.map
1147 -keep public class proguard.gui.ProGuardGUI {
1156 use ProGuard to preverify the class files for Java Micro Edition. ProGuard
1223 (<code>static final</code> fields). ProGuard would therefore list such fields
1254 <h3>Using annotations to configure ProGuard</h3>
1256 The traditional ProGuard configuration allows to keep a clean separation
1262 <code>examples/annotations/lib</code> in the ProGuard distribution.
1264 corresponding ProGuard configuration (or meta-configuration, if you prefer)
1275 The ProGuard configuration file for the application can then be simplified by
