Lines Matching full:jar
84 -injars myapplication.jar
85 -outjars myapplication_out.jar
86 -libraryjars <java.home>/lib/rt.jar
119 output jar, by performing up to 3 optimization passes, and by aggressively
134 -injars in.jar
135 -outjars out.jar
136 -libraryjars <java.home>/lib/rt.jar
143 class in the library <code>rt.jar</code>.
157 -injars in.jar
158 -outjars out.jar
159 -libraryjars /usr/local/java/wtk2.5.2/lib/midpapi20.jar
160 -libraryjars /usr/local/java/wtk2.5.2/lib/cldcapi11.jar
170 <code>midpapi20.jar</code> and <code>cldcapi11.jar</code>, instead of the Java
171 Standard Edition run-time environment <code>rt.jar</code>. You can target
176 class in the library <code>midpapi20.jar</code>.
192 Note that you will still have to adapt the midlet jar size in the
200 -injars in.jar
201 -outjars out.jar
202 -libraryjars /usr/local/java/javacard2.2.2/lib/api.jar
220 -injars in.jar
221 -outjars out.jar
222 -libraryjars /usr/local/java/jtv1.1/javatv.jar
223 -libraryjars /usr/local/java/cdc1.1/lib/cdc.jar
241 -outjars bin/classes-processed.jar
242 -libraryjars /usr/local/java/android-sdk/platforms/android-9/android.jar
311 -outjars bin/classes-processed.jar
312 -libraryjars /usr/local/java/android-sdk/platforms/android-9/android.jar
391 -libraryjars /usr/local/android-sdk/add-ons/google_apis-7_r01/libs/maps.jar
424 -injars in.jar
425 -outjars out.jar
426 -libraryjars <java.home>/lib/rt.jar
506 <code>in.jar</code>:
508 -injars in.jar
509 -outjars out.jar
510 -libraryjars <java.home>/lib/rt.jar
537 <code>in.jar</code>:
539 -injars in.jar
540 -outjars out.jar
541 -libraryjars <java.home>/lib/rt.jar
562 <code>in.jar</code>:
564 -injars in.jar
565 -outjars out.jar
566 -libraryjars /usr/local/java/wtk2.5.2/lib/midpapi20.jar
567 -libraryjars /usr/local/java/wtk2.5.2/lib/cldcapi11.jar
596 Note that you will still have to adapt the midlet jar size in the
602 <code>in.jar</code>:
604 -injars in.jar
605 -outjars out.jar
606 -libraryjars /usr/local/java/javacard2.2.2/lib/api.jar
625 <code>in.jar</code>:
627 -injars in.jar
628 -outjars out.jar
629 -libraryjars /usr/local/java/jtv1.1/javatv.jar
630 -libraryjars /usr/local/java/cdc1.1/lib/cdc.jar
648 <code>in.jar</code>:
650 -injars in.jar
651 -outjars out.jar
652 -libraryjars <java.home>/lib/rt.jar
653 -libraryjars /usr/local/java/servlet/servlet.jar
660 is not part of the standard run-time jar, so we're specifying it as a library.
681 <code>in.jar</code>:
683 -injars in.jar
684 -injars /usr/local/java/scala-2.9.1/lib/scala-library.jar
685 -outjars out.jar
686 -libraryjars <java.home>/lib/rt.jar
728 runtime library as well. The processed jar can be an order of magnitude
1095 signing information, you should sign the jar again after it has been
1098 If you're merging several input jars into a single output jar, you'll have to
1101 -injars in1.jar
1102 -injars in2.jar(!META-INF/MANIFEST.MF)
1103 -injars in3.jar(!META-INF/MANIFEST.MF)
1104 -outjars out.jar
1107 The filters will let ProGuard copy the manifest file from the first jar and
1277 a single jar. For example:
1280 -injars in1.jar
1281 -injars in2.jar
1282 -injars in3.jar
1283 -outjars out.jar
1287 <code>classes</code> directory and the three jars into a single output jar
1288 <code>out.jar</code>.
1294 -injars in1.jar
1295 -injars in2.jar
1296 -injars in3.jar
1305 -injars in1.jar
1306 -injars in2.jar
1307 -injars in3.jar
1315 -outjars out.jar
1320 <code>out.jar</code>.
1327 -injars base_in1.jar
1328 -injars base_in2.jar
1329 -injars base_in3.jar
1330 -outjars base_out.jar
1332 -injars extra_in.jar
1333 -outjars extra_out.jar
1336 This configuration puts the processed results of all <code>base_in*.jar</code>
1337 jars into <code>base_out.jar</code>, and the processed results of the
1338 <code>extra_in.jar</code> into <code>extra_out.jar</code>. Note that only the
1350 you want to disregard certain files from an input jar:
1352 -injars in.jar(!images/**)
1353 -outjars out.jar
1360 the output. For example, only keeping the manifest file from a first input jar:
1362 -injars in1.jar
1363 -injars in2.jar(!META-INF/MANIFEST.MF)
1364 -injars in3.jar(!META-INF/MANIFEST.MF)
1365 -outjars out.jar
1369 disregarding a large number of irrelevant classes in the runtime library jar:
1371 -libraryjars <java.home>/lib/rt.jar(java/**,javax/**)
1380 -injars in(**/acme_*.jar;)
1381 -outjars out.jar
1384 Note the semi-colon in the filter; the filter in front of it applies to jar
1385 names. In this case, only <code>acme_*.jar</code> jars are read from the
1393 -injars in.jar
1394 -outjars code_out.jar(**.class)
1395 -outjars resources_out.jar
1399 files to <code>code_out.jar</code>, and all remaining files to
1400 <code>resources_out.jar</code>.
1413 input in this directory, using the original jar names. For example, showing
1416 -injars application1.jar
1417 -injars application2.jar
1418 -injars application3.jar
1431 -injars proguardgui.jar
1432 -outjars proguardgui_out.jar
1433 -injars proguard.jar
1434 -outjars proguard_out.jar
1435 -libraryjars <java.home>/lib/rt.jar
1448 ProGuard jar and the additional obfuscated GUI jar.
1451 original code. The <code>proguard_out.jar</code> will be identical to the one
1458 jar will always remain usable without changes. You can then specify the base
1459 jar as a library jar:
1461 -injars proguardgui.jar
1462 -outjars proguardgui_out.jar
1463 -libraryjars proguard.jar
1464 -libraryjars <java.home>/lib/rt.jar
1480 -injars in.jar
1481 -outjars out.jar
1482 -libraryjars /usr/local/java/wtk2.5.2/lib/midpapi20.jar
1483 -libraryjars /usr/local/java/wtk2.5.2/lib/cldcapi11.jar
1504 -injars in.jar
1505 -outjars out.jar
1506 -libraryjars <java.home>/lib/rt.jar
1526 -injars in.jar
1527 -libraryjars <java.home>/lib/rt.jar
1539 We're not specifying an output jar, just printing out some results. We're
1558 jar:
1560 -injars in.jar
1570 Note how we don't need to specify the Java run-time jar, because we're not
1571 processing the input jar at all.
1582 The annotation classes are defined in <code>annotations.jar</code>. The
1597 -injars in.jar
1598 -outjars out.jar
1599 -libraryjars <java.home>/lib/rt.jar