unpack200 - transform a packed file into a JAR file for web deployment
unpack200 [options] input-file JAR-file
pack200 gzip file or a pack200 file. The input can also be a JAR file produced by pack200 with an effort of 0, in which case the contents of the input file are copied to the output JAR file with the pack200 marker.
The unpack200 command is a native implementation that transforms a packed file produced by the 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
-Hvalue or --deflate-hint=valuetrue, false, or keep on all entries within a JAR file. The default mode is keep. If the value is true or false, then the --deflate=hint option overrides the default behavior and sets the deflation mode on all entries within the output JAR file.
-r or --remove-pack-file-v or --verbose-q or --quiet-l filename or --log-file=filename-? or -h or --helpunpack200 command.
-V or --versionunpack200 command.
-Joptionoption is one of the options described on the reference page for the Java application launcher. For example, -J-Xms48m sets 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.