Lines Matching full:files
19 files. Typically, you'll put most options in a configuration file (say,
24 You can combine command line options and options from configuration files, for
39 lines in configuration files. This means that you can quote any arbitrary
90 application to be processed. The class files in these jars will be
91 processed and written to the output jars. By default, any non-class files
92 will be copied without changes. Please be aware of any temporary files
93 (e.g. created by IDEs), especially if you are reading your input files
111 You must avoid letting the output files overwrite any input files. For
120 application to be processed. The files in these jars will not be included
122 class files that are <i>extended</i> by application class files. Library
123 class files that are only <i>called</i> needn't be present, although their
174 <dd>Specifies the version number to be set in the processed class files. The
178 default, the version numbers of the class files are left unchanged. For
180 files to Java 6</a>, by changing their version numbers and having them
187 specified input, output, and configuration files or directories.</dd>
289 <dd>Specifies not to shrink the input class files. By default, shrinking is
299 <dd>Specifies to list dead code of the input class files. The list is printed
328 <dd>Specifies not to optimize the input class files. By default, optimization
416 <dd>Specifies not to obfuscate the input class files. By default, obfuscation
419 Internal attributes that are useful for debugging, such as source files
460 specifying strings that are typically already present in class files (such
490 <i>Counter-indication:</i> the resulting class files fall within the Java
549 class files overwrite each other. Code that self-destructs when it's
575 <dd>Specifies to repackage all class files that are renamed, by moving them
586 <i>Counter-indication:</i> classes that look for resource files in their
622 files.
644 <dd>Specifies the resource files to be renamed, based on the obfuscated names
645 of the corresponding class files (if any). Without a filter, all resource
646 files that correspond to class files are renamed. With a filter, only
647 matching files are renamed. For example, see <a
648 href="examples.html#resourcefiles">processing resource files</a>. Only
654 <dd>Specifies the resource files whose contents are to be updated. Any class
655 names mentioned in the resource files are renamed, based on the obfuscated
657 contents of all resource files updated. With a filter, only matching files
658 are updated. The resource files are parsed and written using the
662 see <a href="examples.html#resourcefiles">processing resource files</a>.
674 <dd>Specifies not to preverify the processed class files. By default, class
675 files are preverified if they are targeted at Java Micro Edition or at
684 <dd>Specifies that the processed class files are targeted at Java Micro
735 included files and replaced variables. The structure is printed to the
743 <dd>Specifies to write out the internal structure of the class files, after
755 ProGuard accepts a generalization of class paths to specify input files and
756 output files. A class path consists of entries, separated by the traditional
770 The paths of directly specified class files and resource files is ignored, so
771 class files should generally be part of a jar file, a war file, an ear file, a
772 zip file, or a directory. In addition, the paths of class files should not have
778 <li>A jar file, in which all processed class files and resource files will be
795 Files and directories can be specified as discussed in the section on <a
822 class files in the <code>java</code> and <code>javax</code> directories inside
825 For example, "<code>input.jar(!**.gif,images/**)</code>" matches all files in
827 gif files.
834 considers jar files in the <code>lib</code> and <code>support</code>
835 directories in the <code>input</code> war, not any other jar files. It then
836 matches all class files and gif files that are encountered.
879 comma-separated list of file names that can contain wildcards. Only files with
895 class files in the <code>java</code> and <code>javax</code>.
902 For example, "<code>!**.gif,images/**</code>" matches all files in the
903 <code>images</code> directory, except gif files.
912 configuration: names of files, directories, classes, packages, attributes,
1072 files.
