Home | History | Annotate | Download | only in manual

Lines Matching full:jars

162     the program jars or library jars. You should check whether the name is
219 <dd>Your program jars or library jars contain multiple definitions of the
223 so is by specifying filters on the input jars or library jars. You can
229 specifies the input jars for you. There may not be an easy way to filter
232 input jars yourself (with <code>-injars</code> or
243 <dd>Your input jars contain multiple resource files with the same name.
247 convenient way to do so is by specifying filters on the input jars. There
252 specifies the input jars for you. There may not be an easy way to filter
265 <dd>A class in one of your program jars or library jars is referring to a
315 specifies the input jars for you. Unfortunately, many pre-compiled
547 jars from your configuration, or by filtering out
659 version of ProGuard. You can just copy the ProGuard jars
676 <code>preverify</code> tool always unpacks the jars, so class files with
713 library jars and, of course, your processed program jar.</dd>
754 simply copies resource files over from the input jars to the output jars.
907 Furthermore, you should check whether you have specified your program jars
908 and library jars properly. Program classes can refer to library classes,