Lines Matching full:jar
60 java -jar proguard.jar @proguard.pro
65 -injars proguard.jar
66 -outjars proguard_out.jar
67 -libraryjars <java.home>/lib/rt.jar
98 output jar, by performing up to 3 optimization passes, and by aggressively
114 -injars in.jar
115 -outjars out.jar
116 -libraryjars <java.home>/lib/rt.jar
123 class in the library <code>rt.jar</code>.
137 -injars in.jar
138 -outjars out.jar
139 -libraryjars /usr/local/java/wtk2.1/lib/midpapi20.jar
140 -libraryjars /usr/local/java/wtk2.1/lib/cldcapi11.jar
150 <code>midpapi20.jar</code> and <code>cldcapi11.jar</code>, instead of the Java
151 Standard Edition run-time environment <code>rt.jar</code>. You can target
156 class in the library <code>midpapi20.jar</code>.
172 Note that you will still have to adapt the midlet jar size in the
180 -injars in.jar
181 -outjars out.jar
182 -libraryjars /usr/local/java/javacard2.2.2/lib/api.jar
200 -injars in.jar
201 -outjars out.jar
202 -libraryjars /usr/local/java/jtv1.1/javatv.jar
203 -libraryjars /usr/local/java/cdc1.1/lib/cdc.jar
220 -injars in.jar
221 -outjars out.jar
222 -libraryjars /usr/local/java/android-1.5_r1/platforms/android-1.5/android.jar
247 -injars in.jar
248 -outjars out.jar
249 -libraryjars <java.home>/lib/rt.jar
322 <code>in.jar</code>:
324 -injars in.jar
325 -outjars out.jar
326 -libraryjars <java.home>/lib/rt.jar
353 <code>in.jar</code>:
355 -injars in.jar
356 -outjars out.jar
357 -libraryjars <java.home>/lib/rt.jar
378 <code>in.jar</code>:
380 -injars in.jar
381 -outjars out.jar
382 -libraryjars /usr/local/java/wtk2.1/lib/midpapi20.jar
383 -libraryjars /usr/local/java/wtk2.1/lib/cldcapi11.jar
412 Note that you will still have to adapt the midlet jar size in the
418 <code>in.jar</code>:
420 -injars in.jar
421 -outjars out.jar
422 -libraryjars /usr/local/java/javacard2.2.2/lib/api.jar
441 <code>in.jar</code>:
443 -injars in.jar
444 -outjars out.jar
445 -libraryjars /usr/local/java/jtv1.1/javatv.jar
446 -libraryjars /usr/local/java/cdc1.1/lib/cdc.jar
464 broadcast receivers, and content providers in <code>in.jar</code>:
466 -injars in.jar
467 -outjars out.jar
468 -libraryjars /usr/local/java/android-1.5_r1/platforms/android-1.5/android.jar
494 <code>in.jar</code>:
496 -injars in.jar
497 -outjars out.jar
498 -libraryjars <java.home>/lib/rt.jar
499 -libraryjars /usr/local/java/servlet/servlet.jar
506 is not part of the standard run-time jar, so we're specifying it as a library.
957 a single jar. For example:
960 -injars in1.jar
961 -injars in2.jar
962 -injars in3.jar
963 -outjars out.jar
967 <code>classes</code> directory and the three jars into a single output jar
968 <code>out.jar</code>.
974 -injars in1.jar
975 -injars in2.jar
976 -injars in3.jar
985 -injars in1.jar
986 -injars in2.jar
987 -injars in3.jar
995 -outjars out.jar
1000 <code>out.jar</code>.
1007 -injars base_in1.jar
1008 -injars base_in2.jar
1009 -injars base_in3.jar
1010 -outjars base_out.jar
1012 -injars extra_in.jar
1013 -outjars extra_out.jar
1016 This configuration puts the processed results of all <code>base_in*.jar</code>
1017 jars into <code>base_out.jar</code>, and the processed results of the
1018 <code>extra_in.jar</code> into <code>extra_out.jar</code>. Note that only the
1030 example, if you want to disregard certain files from an input jar:
1032 -injars in.jar(!images/**)
1033 -outjars out.jar
1040 the output. For example, only keeping the manifest file from a first input jar:
1042 -injars in1.jar
1043 -injars in2.jar(!META-INF/MANIFEST.MF)
1044 -injars in3.jar(!META-INF/MANIFEST.MF)
1045 -outjars out.jar
1049 disregarding a large number of irrelevant classes in the runtime library jar:
1051 -libraryjars <java.home>/lib/rt.jar(java/**,javax/**)
1060 -injars in(**/acme_*.jar;)
1061 -outjars out.jar
1064 Note the semi-colon in the filter; the filter in front of it applies to jar
1065 names. In this case, only <code>acme_*.jar</code> jars are read from the
1073 -injars in.jar
1074 -outjars code_out.jar(**.class)
1075 -outjars resources_out.jar
1079 files to <code>code_out.jar</code>, and all remaining files to
1080 <code>resources_out.jar</code>.
1093 input in this directory, using the original jar names. For example, showing
1096 -injars application1.jar
1097 -injars application2.jar
1098 -injars application3.jar
1111 -injars proguardgui.jar
1112 -outjars proguardgui_out.jar
1113 -injars proguard.jar
1114 -outjars proguard_out.jar
1115 -libraryjars <java.home>/lib/rt.jar
1128 ProGuard jar and the additional obfuscated GUI jar.
1131 original code. The <code>proguard_out.jar</code> will be identical to the one
1138 jar will always remain usable without changes. You can then specify the base
1139 jar as a library jar:
1141 -injars proguardgui.jar
1142 -outjars proguardgui_out.jar
1143 -libraryjars proguard.jar
1144 -libraryjars <java.home>/lib/rt.jar
1160 -injars in.jar
1161 -outjars out.jar
1162 -libraryjars /usr/local/java/wtk2.1/lib/midpapi20.jar
1163 -libraryjars /usr/local/java/wtk2.1/lib/cldcapi11.jar
1184 -injars in.jar
1185 -outjars out.jar
1186 -libraryjars <java.home>/lib/rt.jar
1206 -injars in.jar
1207 -libraryjars <java.home>/lib/rt.jar
1219 We're not specifying an output jar, just printing out some results. We're
1238 jar:
1240 -injars in.jar
1250 Note how we don't need to specify the Java run-time jar, because we're not
1251 processing the input jar at all.
1263 The annotation classes are defined in <code>annotations.jar</code>. The
1278 -injars in.jar
1279 -outjars out.jar
1280 -libraryjars <java.home>/lib/rt.jar
