Lines Matching full:jars
98 <dd>Specifies the input jars (or wars, ears, zips, or directories) of the
99 application to be processed. The class files in these jars will be
100 processed and written to the output jars. By default, any non-class files
111 <dd>Specifies the names of the output jars (or wars, ears, zips, or
113 options will be written to the named jars. This allows you to collect the
114 contents of groups of input jars into corresponding groups of output jars.
118 filter, within the group of output jars.
123 no jars will be written.</dd>
128 <dd>Specifies the library jars (or wars, ears, zips, or directories) of the
129 application to be processed. The files in these jars will not be included
130 in the output jars. The specified library jars should at least contain the
149 <dd>Specifies to skip non-public classes while reading library jars, to speed
153 code in the input jars. Ignoring them then speeds up ProGuard, without
178 <dd>Specifies the directories to be kept in the output jars (or wars, ears, or
557 jars. Only if a jar is unpacked on a platform with a case-insensitive
560 unpacked! Developers who really want to unpack their jars on Windows can
561 use this option to switch off this behavior. Note that the obfuscated jars
897 matching file names are read (in the case of input jars), or written (in the
898 case of output jars). The following wildcards are supported:
