unpack200
You use the unpack200 command to transform a packed file into a JAR file for web deployment.
Synopsis
Note:
pack200 and unpack200 have been deprecated and might be removed in a future JDK release.
unpack200 [ options ] input-file JAR-file-
options -
The command-line options. See Options for the unpack200 Command.
-
input-file -
Name of the input file, which can be a
pack200 gzipfile or apack200file. The input can also be a JAR file produced bypack200with an effort of0, in which case the contents of the input file are copied to the output JAR file with thepack200marker. -
JAR-file -
Name of the output JAR file.
Description
The unpack200 command is a native implementation that transforms a packed file produced by pack200 into a JAR file for web deployment. An example of typical usage follows. In the following example, the myarchive.jar file is produced from myarchive.pack.gz with the default unpack200 command settings.
unpack200 myarchive.pack.gz myarchive.jar
Options for the unpack200 Command
-
-Hvalueor--deflate-hint=value -
Sets deflation to be
true,false, orkeepon all entries within a JAR file. The default mode iskeep. If the value istrueorfalse, then the--deflate=hintoption overrides the default behavior and sets the deflation mode on all entries within the output JAR file. -
-ror--remove-pack-file -
Removes the input pack file.
-
-vor--verbose -
Displays minimal messages. Multiple specifications of this option displays more verbose messages.
-
-qor--quiet -
Specifies quiet operation with no messages.
-
-lfilename or--log-file=filename -
Specifies a log file where output messages are logged.
-
-?,-h, or--help -
Prints help information about the
unpack200command. -
-Vor--version -
Prints version information about the
unpack200command. -
-Joption -
Passes option to the Java Virtual Machine, where
optionis one of the options described on the reference page for the Java application launcher. For example,-J-Xms48msets the startup memory to 48 MB.
Notes
This command shouldn’t be confused with the unpack command. They’re distinctly separate products.
The Java SE API Specification provided with the JDK is the superseding authority in case of discrepancies.
Exit Status
The following exit values are returned: 0 for successful completion, and a value that is greater than 0 when an error occurred.