Lines Matching full:configuration
32 configuration file, using embedded ProGuard configuration options, or using
33 the equivalent XML configuration tags. These three ways can be combined,
37 <h3>1. An external ProGuard configuration file</h3>
40 ProGuard configuration file, and include it from Ant. You can include your
41 ProGuard configuration file by setting
42 the <a href="#configuration_attribute"><code>configuration</code></a>
50 <proguard configuration="myconfigfile.pro"/>
54 This is a convenient option if you prefer ProGuard's configuration style over
56 configuration with developers who don't use Ant.
59 <h3>2. Embedded ProGuard configuration options</h3>
61 Instead of keeping an external ProGuard configuration file, you can also copy
95 configuration. Other occurrences of <code><</code> and <code>></code>
99 <h3>3. XML configuration tags</h3>
101 If you really prefer a full-blown XML configuration, you can replace the
102 ProGuard configuration options by XML configuration tags. The resulting
103 configuration will be equivalent, but much more verbose and difficult to read,
106 href="usage.html">Usage</a> section. You can find some sample configuration
120 <dt><a name="configuration_attribute"><code><b>configuration</b></code></a>
122 <dd>Read and merge options from the given ProGuard-style configuration
124 href="#configuration_element"><code>configuration</code></a>
270 <dd>Print notes about potential mistakes or omissions in the configuration.
290 <dd>Write out the entire configuration in traditional ProGuard style, to the
438 <dt><a name="configuration_element"><code><b><configuration refid = </b></code></a>"<i>ref_id</i>"
440 <dd>Includes the configuration specified in the
443 "<i>ref_id</i>". Note that only the nested elements of this configuration
445 configuration files, use the <a
446 href="#configuration_attribute"><code>configuration</code></a>
