Lines Matching full:jars
36 <li><a href="#applications">All possible applications in the input jars</a></li>
37 <li><a href="#applets">All possible applets in the input jars</a></li>
38 <li><a href="#midlets">All possible midlets in the input jars</a></li>
39 <li><a href="#jcapplets">All possible Java Card applets in the input jars</a></li>
40 <li><a href="#xlets">All possible xlets in the input jars</a></li>
41 <li><a href="#servlets">All possible servlets in the input jars</a></li>
172 other JME environments by picking the appropriate jars.
185 unpacks your processed jars, you should then use ProGuard's <a
292 <li>The build processes are already setting the necessary program jars,
293 library jars, and output jars for you — don't specify them again.</li>
503 <h3><a name="applications">All possible applications in the input jars</a></h3>
534 <h3><a name="applets">All possible applets in the input jars</a></h3>
559 <h3><a name="midlets">All possible midlets in the input jars</a></h3>
586 unpacks your processed jars, you should then use ProGuard's <a
599 <h3><a name="jcapplets">All possible Java Card applets in the input jars</a></h3>
622 <h3><a name="xlets">All possible xlets in the input jars</a></h3>
645 <h3><a name="servlets">All possible servlets in the input jars</a></h3>
1098 If you're merging several input jars into a single output jar, you'll have to
1108 ignore any manifest files in the second and third input jars. Note that
1109 ProGuard will leave the order of the files in the jars unchanged; manifest
1287 <code>classes</code> directory and the three jars into a single output jar
1290 If you want to preserve the structure of your input jars (and/or wars, ears,
1300 The input jars will then be reconstructed in the directory <code>out</code>,
1318 This configuration puts the processed contents of all jars inside
1322 If you want to combine input jars (and/or wars, ears, zips, or directories)
1323 into output jars (and/or wars, ears, zips, or directories), you can group the
1337 jars into <code>base_out.jar</code>, and the processed results of the
1349 filtering out zips, ears, wars, jars, and/or ordinary files. For example, if
1377 It is also possible to filter the jars (and/or wars, ears, zips) themselves,
1385 names. In this case, only <code>acme_*.jar</code> jars are read from the
1411 The easiest way is to specify your input jars (and/or wars, ears, zips, and
1423 contain processed versions of application jars, with their original names.
1443 We're reading both unprocessed jars as input. Their processed contents will go
1444 to the respective output jars. The <a
