Lines Matching full:configuration
43 configuration file, using embedded ProGuard configuration options, or using
44 the equivalent XML configuration tags. These three ways can be combined,
48 <h3>1. An external ProGuard configuration file</h3>
51 ProGuard configuration file, and include it from Ant. You can include your
52 ProGuard configuration file by setting
53 the <a href="#configuration_attribute"><code>configuration</code></a>
61 <proguard configuration="myconfigfile.pro"/>
65 This is a convenient option if you prefer ProGuard's configuration style over
67 configuration with developers who don't use Ant.
70 <h3>2. Embedded ProGuard configuration options</h3>
72 Instead of keeping an external ProGuard configuration file, you can also copy
106 configuration. Other occurrences of <code><</code> and <code>></code>
110 <h3>3. XML configuration tags</h3>
112 If you really prefer a full-blown XML configuration, you can replace the
113 ProGuard configuration options by XML configuration tags. The resulting
114 configuration will be equivalent, but much more verbose and difficult to read,
117 href="usage.html">Usage</a> section. You can find some sample configuration
130 <dt><a name="configuration_attribute"><code><b>configuration</b></code></a>
132 <dd>Read and merge options from the given ProGuard-style configuration
134 href="#configuration_element"><code>configuration</code></a>
285 <dd>Print notes about potential mistakes or omissions in the configuration.
305 <dd>Write out the entire configuration in traditional ProGuard style, to the
453 <dt><a name="configuration_element"><code><b><configuration refid = </b></code></a>"<i>ref_id</i>"
455 <dd>Includes the configuration specified in the
458 "<i>ref_id</i>". Note that only the nested elements of this configuration
460 configuration files, use the <a
461 href="#configuration_attribute"><code>configuration</code></a>
