Lines Matching full:configuration
52 You can find some sample configuration files in the <code>examples</code>
58 typically create a configuration file <code>proguard.pro</code> and then type:
63 The configuration file would contain the following options:
191 The configuration is very similar to the configuration for midlets, except that
212 The configuration is very similar to the configuration for midlets, except that
231 The configuration is very similar to the configuration for midlets, except that
283 This configuration should preserve everything we'll ever want to access in the
679 ever be serialized. Knowing your application and tuning the configuration
686 setter methods, then configuration may become painful. There's not much else
862 main application class that is kept by the configuration. All other class names
966 This configuration merges the processed versions of the files in the
998 This configuration puts the processed contents of all jars inside
1016 This configuration puts the processed results of all <code>base_in*.jar</code>
1036 This configuration removes any files in the <code>images</code> directory and
1078 This configuration splits the processed output, sending <code>**.class</code>
1256 The traditional ProGuard configuration allows to keep a clean separation
1257 between the code and the configuration for shrinking, optimization, and
1264 corresponding ProGuard configuration (or meta-configuration, if you prefer)
1275 The ProGuard configuration file for the application can then be simplified by
