1 '\" t 2 .\" Copyright (c) 1997, 2013, Oracle and/or its affiliates. All rights reserved. 3 .\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. 4 .\" 5 .\" This code is free software; you can redistribute it and/or modify it 6 .\" under the terms of the GNU General Public License version 2 only, as 7 .\" published by the Free Software Foundation. 8 .\" 9 .\" This code is distributed in the hope that it will be useful, but WITHOUT 10 .\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 11 .\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 12 .\" version 2 for more details (a copy is included in the LICENSE file that 13 .\" accompanied this code). 14 .\" 15 .\" You should have received a copy of the GNU General Public License version 16 .\" 2 along with this work; if not, write to the Free Software Foundation, 17 .\" Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 18 .\" 19 .\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 20 .\" or visit www.oracle.com if you need additional information or have any 21 .\" questions. 22 .\" 23 .\" Arch: generic 24 .\" Software: JDK 8 25 .\" Date: 21 November 2013 26 .\" SectDesc: Basic Tools 27 .\" Title: jar.1 28 .\" 29 .if n .pl 99999 30 .TH jar 1 "21 November 2013" "JDK 8" "Basic Tools" 31 .\" ----------------------------------------------------------------- 32 .\" * Define some portability stuff 33 .\" ----------------------------------------------------------------- 34 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 35 .\" http://bugs.debian.org/507673 36 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html 37 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 38 .ie \n(.g .ds Aq \(aq 39 .el .ds Aq ' 40 .\" ----------------------------------------------------------------- 41 .\" * set default formatting 42 .\" ----------------------------------------------------------------- 43 .\" disable hyphenation 44 .nh 45 .\" disable justification (adjust text to left margin only) 46 .ad l 47 .\" ----------------------------------------------------------------- 48 .\" * MAIN CONTENT STARTS HERE * 49 .\" ----------------------------------------------------------------- 50 51 .SH NAME 52 jar \- Manipulates Java Archive (JAR) files\&. 53 .SH SYNOPSIS 54 Create JAR file 55 .sp 56 .nf 57 58 \fBjar c\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] 59 .fi 60 .sp 61 62 Update JAR file 63 .sp 64 .nf 65 66 \fBjar u\fR[\fBefmMnv0\fR] [\fIentrypoint\fR] [\fIjarfile\fR] [\fImanifest\fR] [\fB\-C\fR \fIdir\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] 67 .fi 68 .sp 69 70 Extract JAR file 71 .sp 72 .nf 73 74 \fBjar\fR \fBx\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] 75 .fi 76 .sp 77 78 List Contents of JAR file 79 .sp 80 .nf 81 82 \fBjar\fR \fBt\fR[\fBvf\fR] [\fIjarfile\fR] \fIfile\fR \&.\&.\&. [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] 83 .fi 84 .sp 85 86 Add Index to JAR file 87 .sp 88 .nf 89 90 \fBjar\fR \fBi\fR \fIjarfile\fR [\-J\fIoption\fR \&.\&.\&.] [@\fIarg\-file\fR \&.\&.\&.] 91 .fi 92 .sp 93 .SH DESCRIPTION 94 The \f3jar\fR command is a general-purpose archiving and compression tool, based on ZIP and the ZLIB compression format\&. However, the \f3jar\fR command was designed mainly to package Java applets or applications into a single archive\&. When the components of an applet or application (files, images and sounds) are combined into a single archive, they can be downloaded by a Java agent (such as a browser) in a single HTTP transaction, rather than requiring a new connection for each piece\&. This dramatically improves download times\&. The \f3jar\fR command also compresses files, which further improves download time\&. The \f3jar\fR command also allows individual entries in a file to be signed by the applet author so that their origin can be authenticated\&. A JAR file can be used as a class path entry, whether or not it is compressed\&. 95 .PP 96 The syntax for the \f3jar\fR command resembles the syntax for the \f3tar\fR command\&. It has several operation modes, defined by one of the mandatory \fIoperation arguments\fR\&. Other arguments are either \fIoptions\fR that modify the behavior of the operation, or \fIoperands\fR required to perform the operation\&. 97 .SH OPERATION\ ARGUMENTS 98 When using the \f3jar\fR command, you have to select an operation to be performed by specifying one of the following operation arguments\&. You can mix them up with other one-letter options on the command line, but usually the operation argument is the first argument specified\&. 99 .TP 100 c 101 Create a new JAR archive\&. 102 .TP 103 i 104 Generate index information for a JAR archive\&. 105 .TP 106 t 107 List the contents of a JAR archive\&. 108 .TP 109 u 110 Update a JAR archive\&. 111 .TP 112 x 113 Extract files from a JAR archive\&. 114 .SH OPTIONS 115 Use the following options to customize how the JAR file is created, updated, extracted, or viewed: 116 .TP 117 e 118 Sets the class specified by the \fIentrypoint\fR operand to be the entry point\f3\fR for a standalone Java application bundled into an executable JAR file\&. The use of this option creates or overrides the \f3Main-Class\fR attribute value in the manifest file\&. The \f3e\fR option can be used when creating (\f3c\fR) or updating (\f3u\fR) the JAR file\&. 119 120 For example, the following command creates the \f3Main\&.jar\fR archive with the \f3Main\&.class\fR file where the \f3Main-Clas\fRs attribute value in the manifest is set to \f3Main\fR: 121 .sp 122 .nf 123 \f3jar cfe Main\&.jar Main Main\&.class\fP 124 .fi 125 .nf 126 \f3\fP 127 .fi 128 .sp 129 130 131 The Java Runtime Environment (JRE) can directly call this application by running the following command: 132 .sp 133 .nf 134 \f3java \-jar Main\&.jar\fP 135 .fi 136 .nf 137 \f3\fP 138 .fi 139 .sp 140 141 142 If the entry point class name is in a package, then it could use either the dot (\&.) or slash (/) as the delimiter\&. For example, if \f3Main\&.class\fR is in a package called \f3mydir\fR, then the entry point can be specified in one of the following ways: 143 .sp 144 .nf 145 \f3jar \-cfe Main\&.jar mydir/Main mydir/Main\&.class\fP 146 .fi 147 .nf 148 \f3jar \-cfe Main\&.jar mydir\&.Main mydir/Main\&.class\fP 149 .fi 150 .nf 151 \f3\fP 152 .fi 153 .sp 154 155 156 Note 157 158 Specifying both \f3m\fR and \f3e\fR options together when a particular manifest also contains the \f3Main-Class\fR attribute results in an ambiguous \f3Main-Class\fR specification\&. The ambiguity leads to an error and the \f3jar\fR command creation or update operation is terminated\&. 159 .TP 160 f 161 Sets the file specified by the \fI\fR\fIjarfile\fR operand to be the name of the JAR file that is created (\f3c\fR), updated (\f3u\fR), extracted (\f3x\fR) from, or viewed (\f3t\fR)\&. Omitting the \f3f\fR option and the \fIjarfile\fR operand instructs the \f3jar\fR command to accept the JAR file name from \f3stdin\fR (for \f3x\fR and \f3t\fR) or send the JAR \f3\fRfile to \f3stdout\fR (for \f3c\fR and \f3u\fR)\&. 162 .TP 163 m 164 Includes names and values of attributes from the file specified by the \f3manifest\fR operand in the manifest file of the \f3jar\fR command (located in the archive at \f3META-INF/MANIFEST\&.MF\fR)\&. The \f3jar\fR command adds the attribute\(cqs name and value to the JAR file unless an entry already exists with the same name, in which case the \f3jar\fR command updates the value of the attribute\&. The \f3m\fR option can be used when creating (\f3c\fR) or updating (\f3u\fR) the JAR file\&. 165 166 You can add special-purpose name-value attribute pairs to the manifest that are not contained in the default manifest file\&. For example, you can add attributes that specify vendor information, release information, package sealing, or to make JAR-bundled applications executable\&. For examples of using the \f3m\fR option, see Packaging Programs at http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.html 167 .TP 168 M 169 Does not create a manifest file entry (for \f3c\fR and \f3u\fR), or delete a manifest file entry when one exists (for \f3u\fR)\&. The \f3M\fR option can be used when creating (\f3c\fR) or updating (\f3u\fR) the JAR file\&. 170 .TP 171 n 172 When creating (\f3c\fR) a JAR file, this option normalizes the archive so that the content is not affected by the packing and unpacking operations of the pack200(1) command\&. Without this normalization, the signature of a signed JAR can become invalid\&. 173 .TP 174 v 175 Generates verbose output to standard output\&. See Examples\&. 176 .TP 177 0 178 (Zero) Creates (\f3c\fR) or updates (\f3u\fR) the JAR file without using ZIP compression\&. 179 .TP 180 -C \fIdir\fR 181 .br 182 When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, this option temporarily changes the directory while processing files specified by the \fIfile\fR operands\&. Its operation is intended to be similar to the \f3-C\fR option of the UNIX \f3tar\fR utility\&.For example, the following command changes to the \f3classes\fR directory and adds the \f3Bar\&.class\fR file from that directory to \f3my\&.jar\fR: 183 .sp 184 .nf 185 \f3jar uf my\&.jar \-C classes Bar\&.class\fP 186 .fi 187 .nf 188 \f3\fP 189 .fi 190 .sp 191 192 193 The following command changes to the \f3classes\fR directory and adds to \f3my\&.jar\fR all files within the classes directory (without creating a \f3classes\fR directory in the JAR file), then changes back to the original directory before changing to the \f3bin\fR directory to add \f3Xyz\&.class\fR to \f3my\&.jar\fR\&. 194 .sp 195 .nf 196 \f3jar uf my\&.jar \-C classes \&. \-C bin Xyz\&.class\fP 197 .fi 198 .nf 199 \f3\fP 200 .fi 201 .sp 202 203 204 If \f3classes\fR contained files \f3bar1\fR and \f3bar2\fR, then the JAR file will contain the following after running the previous command: 205 .sp 206 .nf 207 \f3% \fIjar tf my\&.jar\fR\fP 208 .fi 209 .nf 210 \f3META\-INF/\fP 211 .fi 212 .nf 213 \f3META\-INF/MANIFEST\&.MF\fP 214 .fi 215 .nf 216 \f3bar1\fP 217 .fi 218 .nf 219 \f3bar2\fP 220 .fi 221 .nf 222 \f3Xyz\&.class\fP 223 .fi 224 .nf 225 \f3\fP 226 .fi 227 .sp 228 229 .TP 230 \fI\fR-J\fIoption\fR 231 Sets the specified JVM option to be used when the JRE runs the JAR file\&. JVM options are described on the reference page for the java(1) command\&. For example, \f3-J-Xms48m\fR sets the startup memory to 48 MB\&. 232 .SH OPERANDS 233 The following operands are recognized by the \f3jar\fR command\&. 234 .TP 235 \fIfile\fR 236 When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, the \fIfile\fR operand defines the path and name of the file or directory that should be added to the archive\&. When extracting (\f3x\fR) or listing the contents (\f3t\fR) of a JAR file, the \fIfile\fR operand defines the path and name of the file to be extrated or listed\&. At least one valid file or directory must be specified\&. Separate multiple \fIfile\fR operands with spaces\&. If the \fIentrypoint\fR, \fIjarfile\fR, or \fImanifest\fR operands are used, the \fIfile\fR operands must be specified after them\&. 237 .TP 238 \fIentrypoint\fR 239 When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, the \fIentrypoint\fR operand defines the name of the class that should be the entry point\f3\fR for a standalone Java application bundled into an executable JAR file\&. The \fIentrypoint\fR operand must be specified if the \f3e\fR option is present\&. 240 .TP 241 \fIjarfile\fR 242 Defines the name of the file to be created (\f3c\fR), updated (\f3u\fR), extracted (\f3x\fR), or viewed (\f3t\fR)\&. The \fIjarfile\fR operand must be specified if the \f3f\fR option is present\&. Omitting the \f3f\fR option and the \fIjarfile\fR operand instructs the \f3jar\fR command to accept the JAR file name from \f3stdin\fR (for \f3x\fR and \f3t\fR) or send the JAR \f3\fRfile to \f3stdout\fR (for \f3c\fR and \f3u\fR)\&. 243 244 When indexing (\f3i\fR) a JAR file, specify the \fIjarfile\fR operand without the \f3f\fR option\&. 245 .TP 246 \fImanifest\fR 247 When creating (\f3c\fR) or updating (\f3u\fR) a JAR file, the \fImanifest\fR operand defines the preexisting manifest files with names and values of attributes to be included in \f3MANIFEST\&.MF\fR in the JAR file\&. The \fImanifest\fR operand must be specified if the \f3f\fR option is present\&. 248 .TP 249 \fI@arg-file\fR 250 To shorten or simplify the \f3jar\fR command, you can specify arguments in a separate text file and pass it to the \f3jar\fR command with the at sign (@) as a prefix\&. When the \f3jar\fR command encounters an argument beginning with the at sign, it expands the contents of that file into the argument list\&. 251 252 An argument file can include options and arguments of the \f3jar\fR command (except the \f3-J\fR options, because they are passed to the launcher, which does not support argument files)\&. The arguments within a file can be separated by spaces or newline characters\&. File names within an argument file are relative to the current directory from which you run the \f3jar\fR command, not relative to the location of the argument file\&. Wild cards, such as the asterisk (*), that might otherwise be expanded by the operating system shell, are not expanded\&. 253 254 The following example, shows how to create a \f3classes\&.list\fR file with names of files from the current directory output by the \f3find\fR command: 255 .sp 256 .nf 257 \f3find \&. \-name \&'*\&.class\&' \-print > classes\&.list\fP 258 .fi 259 .nf 260 \f3\fP 261 .fi 262 .sp 263 264 265 You can then execute the \f3jar\fR command and pass the \f3classes\&.list\fR file to it using the \fI@arg-file\fR syntax: 266 .sp 267 .nf 268 \f3jar cf my\&.jar @classes\&.list\fP 269 .fi 270 .nf 271 \f3\fP 272 .fi 273 .sp 274 275 276 An argument file can be specified with a path, but any file names inside the argument file that have relative paths are relative to the current working directory of the \f3jar\fR command, not to the path passed in, for example: 277 .sp 278 .nf 279 \f3jar @dir/classes\&.list\fP 280 .fi 281 .nf 282 \f3\fP 283 .fi 284 .sp 285 286 .SH NOTES 287 The \f3e\fR, \f3f\fR, and \f3m\fR options must appear in the same order on the command line as the \fIentrypoint\fR, \fIjarfile\fR, and \fImanifest\fR operands, for example: 288 .sp 289 .nf 290 \f3jar cmef myManifestFile MyMainClass myFile\&.jar *\&.class\fP 291 .fi 292 .nf 293 \f3\fP 294 .fi 295 .sp 296 .SH EXAMPLES 297 \f3Example 1 Adding All Files From the Current Directory With Verbose Output\fR 298 .sp 299 .nf 300 \f3% ls\fP 301 .fi 302 .nf 303 \f31\&.au Animator\&.class monkey\&.jpg\fP 304 .fi 305 .nf 306 \f32\&.au Wave\&.class spacemusic\&.au\fP 307 .fi 308 .nf 309 \f33\&.au at_work\&.gif\fP 310 .fi 311 .nf 312 \f3\fP 313 .fi 314 .nf 315 \f3% jar cvf bundle\&.jar *\fP 316 .fi 317 .nf 318 \f3added manifest\fP 319 .fi 320 .nf 321 \f3adding: 1\&.au(in = 2324) (out= 67)(deflated 97%)\fP 322 .fi 323 .nf 324 \f3adding: 2\&.au(in = 6970) (out= 90)(deflated 98%)\fP 325 .fi 326 .nf 327 \f3adding: 3\&.au(in = 11616) (out= 108)(deflated 99%)\fP 328 .fi 329 .nf 330 \f3adding: Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fP 331 .fi 332 .nf 333 \f3adding: Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fP 334 .fi 335 .nf 336 \f3adding: at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fP 337 .fi 338 .nf 339 \f3adding: monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fP 340 .fi 341 .nf 342 \f3adding: spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fP 343 .fi 344 .nf 345 \f3\fP 346 .fi 347 .sp 348 \f3Example 2 Adding Files From Subdirectories\fR 349 .sp 350 .nf 351 \f3% ls \-F\fP 352 .fi 353 .nf 354 \f3audio/ classes/ images/\fP 355 .fi 356 .nf 357 \f3% jar cvf bundle\&.jar audio classes images\fP 358 .fi 359 .nf 360 \f3added manifest\fP 361 .fi 362 .nf 363 \f3adding: audio/(in = 0) (out= 0)(stored 0%)\fP 364 .fi 365 .nf 366 \f3adding: audio/1\&.au(in = 2324) (out= 67)(deflated 97%)\fP 367 .fi 368 .nf 369 \f3adding: audio/2\&.au(in = 6970) (out= 90)(deflated 98%)\fP 370 .fi 371 .nf 372 \f3adding: audio/3\&.au(in = 11616) (out= 108)(deflated 99%)\fP 373 .fi 374 .nf 375 \f3adding: audio/spacemusic\&.au(in = 3079) (out= 73)(deflated 97%)\fP 376 .fi 377 .nf 378 \f3adding: classes/(in = 0) (out= 0)(stored 0%)\fP 379 .fi 380 .nf 381 \f3adding: classes/Animator\&.class(in = 2266) (out= 66)(deflated 97%)\fP 382 .fi 383 .nf 384 \f3adding: classes/Wave\&.class(in = 3778) (out= 81)(deflated 97%)\fP 385 .fi 386 .nf 387 \f3adding: images/(in = 0) (out= 0)(stored 0%)\fP 388 .fi 389 .nf 390 \f3adding: images/monkey\&.jpg(in = 7667) (out= 91)(deflated 98%)\fP 391 .fi 392 .nf 393 \f3adding: images/at_work\&.gif(in = 6621) (out= 89)(deflated 98%)\fP 394 .fi 395 .nf 396 \f3\fP 397 .fi 398 .nf 399 \f3% ls \-F\fP 400 .fi 401 .nf 402 \f3audio/ bundle\&.jar classes/ images/\fP 403 .fi 404 .nf 405 \f3\fP 406 .fi 407 .sp 408 \f3Example 3 Listing the Contents of JAR\fR 409 .sp 410 .nf 411 \f3% jar tf bundle\&.jar\fP 412 .fi 413 .sp 414 .sp 415 .nf 416 \f3META\-INF/\fP 417 .fi 418 .nf 419 \f3META\-INF/MANIFEST\&.MF\fP 420 .fi 421 .nf 422 \f3audio/1\&.au\fP 423 .fi 424 .nf 425 \f3audio/2\&.au\fP 426 .fi 427 .nf 428 \f3audio/3\&.au\fP 429 .fi 430 .nf 431 \f3audio/spacemusic\&.au\fP 432 .fi 433 .nf 434 \f3classes/Animator\&.class\fP 435 .fi 436 .nf 437 \f3classes/Wave\&.class\fP 438 .fi 439 .nf 440 \f3images/monkey\&.jpg\fP 441 .fi 442 .nf 443 \f3images/at_work\&.gif\fP 444 .fi 445 .nf 446 \f3\fP 447 .fi 448 .sp 449 \f3Example 4 Adding an Index\fR 450 .PP 451 Use the \f3i\fR option when you split the interdependent classes for a stock trade application into three JAR files: \f3main\&.jar\fR, \f3buy\&.jar\fR, and \f3sell\&.jar\fR\&. If you specify the \f3Class-Path\fR attribute in the \f3main\&.jar\fR manifest, then you can use the \f3i\fR option to speed up the class loading time for your application: 452 .sp 453 .nf 454 \f3Class\-Path: buy\&.jar sell\&.jar\fP 455 .fi 456 .nf 457 \f3jar i main\&.jar\fP 458 .fi 459 .nf 460 \f3\fP 461 .fi 462 .sp 463 An \f3INDEX\&.LIST\fR file is inserted to the \f3META-INF\fR directory\&. This enables the application class loader to download the specified JAR files when it is searching for classes or resources\&. 464 .PP 465 The application class loader uses the information stored in this file for efficient class loading\&. To copy directories, first compress files in \f3dir1\fR to \f3stdout\fR, then pipeline and extract from \f3stdin\fR to \f3dir2\fR (omitting the \f3-f\fR option from both \f3jar\fR commands): 466 .sp 467 .nf 468 \f3(cd dir1; jar c \&.) | (cd dir2; jar x)\fP 469 .fi 470 .nf 471 \f3\fP 472 .fi 473 .sp 474 .SH SEE\ ALSO 475 .TP 0.2i 476 \(bu 477 pack200(1)\&. 478 .TP 0.2i 479 \(bu 480 The JAR section of The Java Tutorials at http://docs\&.oracle\&.com/javase/tutorial/deployment/jar/index\&.html 481 .RE 482 .br 483 'pl 8.5i 484 'bp