Lines Matching full:proguard
7 <title>ProGuard Examples</title>
62 <li><a href="#annotated">Using annotations to configure ProGuard</a></li>
66 directory of the ProGuard distribution.
74 bin/proguard @myconfig.pro
90 Note the use of the <code><java.home></code> system property. ProGuard
181 unpacks your processed jars, you should then use ProGuard's <a
189 corresponding jad file; ProGuard doesn't do that for you.
209 have java.lang.Class, so we're telling ProGuard not to worry about it.
331 primitive fields, so ProGuard can generally remove all these classes entirely
348 following line, to let ProGuard know it's ok that the library references some
360 the ProGuard distribution.
363 integrates ProGuard by default. You only need to enable it (for release
364 builds) by adding <code>proguard.config=proguard.cfg</code> to the file
366 the automatically generated file <code>proguard.cfg</code> contains the
371 href="http://developer.android.com/guide/developing/tools/proguard.html">Developer
429 the <code>.class</code> construct. ProGuard will automatically detect them and
543 unpacks your processed jars, you should then use ProGuard's <a
554 corresponding jad file; ProGuard doesn't do that for you.
623 as far as ProGuard is concerned.
690 ProGuard not to complain about some artefacts in the Scala runtime, the way it
721 ProGuard doesn't look at your native code, so it won't automatically preserve
904 adapt the execution behavior accordingly. By default, ProGuard treats
936 This option also gets rid of the note that ProGuard prints out about
959 ProGuard first and then invoke the <code>rmic</code> tool. If that is not
1004 ordinary resource files. ProGuard can adapt obfuscated class names in the
1019 The filters will let ProGuard copy the manifest file from the first jar and
1021 ProGuard will leave the order of the files in the jars unchanged; manifest
1224 This grouping, archiving, and flattening can be arbitrarily complex. ProGuard
1251 Another useful application is speeding up the processing by ProGuard, by
1257 The filter makes ProGuard disregard <code>com.sun.**</code> classes, for
1291 midlets,...) in one go, in order to save time and effort. ProGuard's input and
1295 directories) and a single output directory. ProGuard will then reconstruct the
1311 ProGuard itself, you can still incrementally add other pieces of code that
1312 depend on it, e.g. the ProGuard GUI:
1316 -injars proguard.jar
1319 -applymapping proguard.map
1321 -keep public class proguard.gui.ProGuardGUI {
1329 makes sure the ProGuard part of the code gets the previously produced
1331 ProGuard jar and the additional obfuscated GUI jar.
1346 -libraryjars proguard.jar
1348 -applymapping proguard.map
1350 -keep public class proguard.gui.ProGuardGUI {
1359 use ProGuard to preverify the class files for Java Micro Edition. ProGuard
1426 (<code>static final</code> fields). ProGuard would therefore list such fields
1456 <h3><a name="annotated">Using annotations to configure ProGuard</a></h3>
1458 The traditional ProGuard configuration allows to keep a clean separation
1464 <code>examples/annotations/lib</code> in the ProGuard distribution.
1466 corresponding ProGuard configuration (or meta-configuration, if you prefer)
1477 The ProGuard configuration file for the application can then be simplified by
