You use the
unpack200 command to transform a packed file into a JAR file for web deployment.
unpack200 have been deprecated and might be removed in a future JDK release.
unpack200 [ options ] input-file JAR-file
The command-line options. See Options for the unpack200 Command.
Name of the input file, which can be a
pack200 gzipfile or a
pack200file. The input can also be a JAR file produced by
pack200with an effort of
0, in which case the contents of the input file are copied to the output JAR file with the
Name of the output JAR file.
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
Sets deflation to be
keepon all entries within a JAR file. The default mode is
keep. If the value is
false, then the
--deflate=hintoption overrides the default behavior and sets the deflation mode on all entries within the output JAR file.
Removes the input pack file.
Displays minimal messages. Multiple specifications of this option displays more verbose messages.
Specifies quiet operation with no messages.
Specifies a log file where output messages are logged.
Prints help information about the
Prints version information about the
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.
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.
The following exit values are returned: 0 for successful completion, and a value that is greater than 0 when an error occurred.