changeset 5940:a09aab639ad0

RT-34522: Update javafxpackager man pages for JDK/FX 8 Contributed-by: Nancy Hildebrandt
author kcr
date Mon, 09 Dec 2013 18:52:57 -0800
parents c818e4054cc7
children f1d3a11f6cc4
files modules/fxpackager/src/main/man/html/javafxpackager.1.html modules/fxpackager/src/main/man/man1/javafxpackager.1
diffstat 2 files changed, 398 insertions(+), 692 deletions(-) [+]
line wrap: on
line diff
--- a/modules/fxpackager/src/main/man/html/javafxpackager.1.html	Mon Dec 09 18:29:48 2013 -0800
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,201 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html lang="en-US" xmlns="http://www.w3.org/1999/xhtml" xml:lang=
-"en-US">
-<head>
-<title>javafxpackager Command Line</title>
-<meta http-equiv="Content-Type" content=
-"text/html; charset=utf-8" />
-<meta name="collection" content="reference" />
-<meta name="copyright" content="2008, 2012"/>
-</head>
-
-<body>
-<h1>javafxpackager Command Line
-</h1>
-<h2>NAME</h2>
-<p><code>javafxpackager</code> - A tool with commands that perform tasks related to
-  packaging and signing JavaFX applications.</p>
-<h2>SYNOPSIS</h2>
-<p><code>javafxpackager -taskcommand [-options]</code></p>
-<p>where <code>-taskcommand</code> is one of the following:</p>
-<p><code>-createjar</code></p>
-<p>Produces a JAR archive according to other parameters.</p>
-<p><code>-deploy</code></p>
-<p>Generates the JNLP and HTML files according to other parameters.</p>
-<p><code>-createbss</code></p>
-<p>Converts CSS files into binary form.</p>
-<p><code>-signJar</code></p>
-<p>Signs JAR file(s) with a provided certificate.</p>
-<p><code>-makeall</code></p>
-<p>Performs compilation, createjar, and deploy steps as one call, with
-  most arguments predefined. The source files must be located in a
-  folder called src, and the resulting files (JAR, JNLP, HTML) are
-  put in a folder called dist. This command can only be configured in
-  a minimal way and is as automated as possible.</p>
-<h2>OPTIONS FOR THE CREATEJAR COMMAND</h2>
-<p><code>-appclass &lt;application class&gt;</code></p>
-<p>Qualified name of the application class to be executed.</p>
-<p><code>-preloader &lt;preloader class&gt;</code></p>
-<p>Qualified name of the preloader class to be executed.</p>
-<p><code>-paramfile &lt;file&gt;</code></p>
-<p>A properties file with default named application parameters.</p>
-<p><code>-argument arg</code></p>
-<p>An unnamed argument to be inserted into the JNLP file as an
-<code>&lt;fx:argument&gt;</code> element.</p>
-<p><code>-classpath &lt;files&gt;</code></p>
-<p>List of dependent JAR file names.</p>
-<p><code>-manifestAttrs &lt;manifest attributes&gt;</code></p>
-<p>List of additional manifest attributes. Syntax:</p>
-<p><code>&quot;name1=value1,name2=value2,name3=value3&quot;</code></p>
-<p><code>-noembedlauncher</code></p>
-<p>If present, the packager will not add the JavaFX launcher classes
-  to the JAR file.</p>
-<p><code>-nocss2bin</code></p>
-<p>The packager will not convert CSS files to binary form before
-  copying to JAR.</p>
-<p><code>-runtimeversion &lt;version&gt;</code></p>
-<p>Version of the required JavaFX Runtime.</p>
-<p><code>-outdir &lt;dir&gt;</code></p>
-<p>Name of the directory that will receive generated output files.</p>
-<p><code>-outfile &lt;filename&gt;</code></p>
-<p>Name (without the extension) of the file that will be generated.</p>
-<p><code>-srcdir &lt;dir&gt;</code></p>
-<p>Base directory of the files to package.</p>
-<p><code>-srcfiles &lt;files&gt;</code></p>
-<p>List of files in srcdir. If omitted, all files in <code>srcdir</code> (which is a mandatory 
-argument in this case) will be used.</p>
-<h2>OPTIONS FOR THE DEPLOY COMMAND</h2>
-<p><code>-title &lt;title&gt;</code></p>
-<p>Title of the application.</p>
-<p><code>-vendor &lt;vendor&gt;</code></p>
-<p>Vendor of the application.</p>
-<p><code>-description &lt;description&gt;</code></p>
-<p>Description of the application.</p>
-<p><code>-appclass &lt;application class&gt;</code></p>
-<p>Qualified name of the application class to be executed.</p>
-<p><code>-preloader &lt;preloader class&gt;</code></p>
-<p>Qualified name of the preloader class to be executed.</p>
-<p><code>-paramfile &lt;file&gt;</code></p>
-<p>Properties file with default named application parameters.</p>
-<p><code>-htmlparamfile &lt;file&gt;</code></p>
-<p>Properties file with parameters for the resulting application when
-  it is run in the browser.</p>
-<p><code>-width &lt;width&gt;</code></p>
-<p>Width of the application.</p>
-<p><code>-height &lt;height&gt;</code></p>
-<p>Height of the application.</p>
-<p><code>-native &lt;type&gt;</code></p>
-<p>Generate self-contained application bundles (if possible). If type
-           is specified, then only a bundle of this type is created. List of
-           supported types includes: installer, image, exe, msi, dmg, rpm,
-           deb.</p>
-<p><code>-name &lt;name&gt;</code></p>
-<p>Name of the application.</p>
-<p><code>-embedjnlp</code></p>
-<p>If present, the JNLP file will be embedded in the HTML document.</p>
-<p><code>-embedCertificates</code></p>
-<p>If present, the certificates will be embedded in the JNLP file.</p>
-<p><code>-allpermissions</code></p>
-<p>If present, the application will require all security permissions
-  in the JNLP file.</p>
-<p><code>-updatemode &lt;updatemode&gt;</code></p>
-<p>Sets the update mode for the JNLP file.</p>
-<p><code>-isExtension</code></p>
-<p>If present, the srcfiles are treated as extensions.</p>
-<p><code>-callbacks</code></p>
-<p>Specifies user callback methods in generated HTML. The format is
-  the following:</p>
-<p><code>&quot;name1:value1,name2:value2,...&quot;</code></p>
-<p><code>-templateInFilename</code></p>
-<p>Name of the HTML template file. Placeholders are in the following
-  form:<br />
-<code>#XXXX.YYYY(APPID)#</code></p>
-<p><code>-templateOutFilename</code></p>
-<p>Name of the HTML file that will be generated from the template.</p>
-<p><code>-templateId</code></p>
-<p>Application ID of the application for template processing.</p>
-<p><code>-argument arg</code></p>
-<p>An unnamed argument to be inserted into an &lt;fx:argument&gt; element in
-  the JNLP file.</p>
-<p><code>-outdir &lt;dir&gt;</code></p>
-<p>Name of the directory that will receive generated output files.</p>
-<p><code>-outfile &lt;filename&gt;</code></p>
-<p>Name (without the extension) of the file that will be generated.</p>
-<p><code>-srcdir &lt;dir&gt;</code></p>
-<p>Base directory of the files to package.</p>
-<p><code>-srcfiles &lt;files&gt;</code></p>
-<p>List of files in srcdir. If omitted, all files in <code>srcdir</code> (which is a mandatory argument in this case) will be used.</p>
-<h2>OPTIONS FOR THE CREATEBSS COMMAND</h2>
-<p><code>-outdir &lt;dir&gt;</code></p>
-<p>Name of the directory that will receive generated output files.</p>
-<p><code>-srcdir &lt;dir&gt;</code></p>
-<p>Base directory of the files to package.</p>
-<p><code>-srcfiles &lt;files&gt;</code></p>
-<p>List of files in srcdir. If omitted, all files in <code>srcdir</code> (which is a mandatory argument in this case) will be used.</p>
-<h2>OPTIONS FOR THE SIGNJAR COMMAND</h2>
-<p><code>-keyStore &lt;file&gt;</code></p>
-<p>Keystore file name.</p>
-<p><code>-alias</code></p>
-<p>Alias for the key.</p>
-<p><code>-storePass</code></p>
-<p>Password to check integrity of the keystore or unlock the keystore</p>
-<p><code>-keyPass</code></p>
-<p>Password for recovering the key.</p>
-<p><code>-storeType</code></p>
-<p>Keystore type. The default value is &quot;jks&quot;.</p>
-<p><code>-outdir &lt;dir&gt;</code></p>
-<p>Name of the directory that will receive generated output files.</p>
-<p><code>-srcdir &lt;dir&gt;</code></p>
-<p>Base directory of the files to be signed.</p>
-<p><code>-srcfiles &lt;files&gt;</code></p>
-<p>List of files in srcdir. If omitted, all files in <code>srcdir</code> (which is a mandatory argument in this case) will be used.</p>
-<h2>OPTIONS FOR THE MAKEALL COMMAND</h2>
-<p><code>-appclass &lt;application class&gt;</code></p>
-<p>Qualified name of the application class to be executed.</p>
-<p><code>-preloader &lt;preloader class&gt;</code></p>
-<p>Qualified name of the preloader class to be executed.</p>
-<p><code>-classpath &lt;files&gt;</code></p>
-<p>List of dependent JAR file names.</p>
-<p><code>-name &lt;name&gt;</code></p>
-<p>Name of the application.</p>
-<p><code>-width &lt;width&gt;</code></p>
-<p>Width of the application.</p>
-<p><code>-height &lt;height&gt;</code></p>
-<p>Height of the application.</p>
-<h2>NOTES</h2>
-<p>A <code>-v</code> option can be used with any task command to enable verbose
-  output.</p>
-<p>When the <code>-srcdir</code> option is allowed in a command, it can be used
-  more than once. If the <code>-srcfiles</code> option is specified, the files
-  named in the argument will be looked for in the location specified
-  in the preceding srcdir option. In case there is no <code>-srcdir</code>  preceding <code>-srcfiles</code>, the directory where the javafxpackager command
-  is executed will be used.</p>
-<h2>EXAMPLES</h2>
-<p>Example 1, -createjar Command Usage</p>
-<p><code>javafxpackager -createjar -appclass package.ClassName<br />
-  -srcdir classes -outdir out -outfile outjar -v</code></p>
-<p>Packages the contents of the classes directory to outjar.jar, sets
-  the application class to package.ClassName.<br /></p>
-<p> Example 2, -deploy Command Usage</p>
-<p><code>javafxpackager -deploy -outdir outdir -outfile outfile -width 34 -height 43<br />
-  -name AppName -appclass package.ClassName -v -srcdir compiled</code></p>
-<p>Generates outfile.jnlp and the corresponding outfile.html files in
-  outdir for application AppName, which is started by package.ClassName
-  and has dimensions of 34 x 43.<br /></p>
-<p>Example 3, -makeall command Usage</p>
-<p><code>javafxpackager -makeall -appclass brickbreaker.Main -name BrickBreaker<br />
-  -width 600 -height 600</code></p>
-<p>Does all the packaging work including compilation: compile,
-  createjar, deploy.<br /></p>
-<p>Example 4, -signJar Command Usage</p>
-<p><code>javafxpackager -signJar --outdir dist -keyStore sampleKeystore.jks<br />
--storePass **** -alias javafx -keypass **** -srcdir dist</code></p>
-<p>Signs all of the JAR files in the dist directory, attaches a
-  certificate with the specified alias, keyStore and storePass, and
-  puts the signed JAR files back into the dist directory.</p>
-
-
-</body>
-</html>
--- a/modules/fxpackager/src/main/man/man1/javafxpackager.1	Mon Dec 09 18:29:48 2013 -0800
+++ b/modules/fxpackager/src/main/man/man1/javafxpackager.1	Mon Dec 09 18:52:57 2013 -0800
@@ -1,13 +1,13 @@
 '\" t
-.\" Copyright \(co 2008, 2012, Oracle. All Rights Reserved.
-.\" Title: javafxpackager
-.\" Language: English
-.\" Date: October 2012
-.\" SectDesc: User Commands
-.\" Software: Oracle Java
-.\" Arch: Generic
+.\"  Copyright (c) 1994, 2013, Oracle and/or its affiliates. All rights reserved.
+.\"     Arch: Generic
+.\"     Software: Oracle Java
+.\"     Date: August 2013
+.\"     SectDesc: User Commands
+.\"     Title: javafxpackager.1
 .\"
-.TH "javafxpackager" "1" "October 2012" "" ""
+.if n .pl 99999
+.TH javafxpackager 1 "August 2013" "Oracle Java" "User Commands"
 .\" -----------------------------------------------------------------
 .\" * Define some portability stuff
 .\" -----------------------------------------------------------------
@@ -27,487 +27,394 @@
 .\" -----------------------------------------------------------------
 .\" * MAIN CONTENT STARTS HERE *
 .\" -----------------------------------------------------------------
-.SH "NAME"
-javafxpackager \- A tool with commands that perform tasks related to packaging and signing JavaFX applications\&.
-.SH "SYNOPSIS"
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-javafxpackager \fI\-taskcommand\fR \fI[\-options]\fR
-.fi
-.if n \{\
+
+.SH NAME    
+javafxpackager \- Performs tasks related to packaging and signing JavaFX applications\&.
+.SH SYNOPSIS    
+.sp     
+.nf     
+
+\fBjavafxpackager\fR \fIcommand\fR [\fIoptions\fR]
+.fi     
+.nf     
+.fi     
+.sp     
+.TP     
+\fIcommand\fR
+The task that should be performed\&.
+.TP     
+options
+One or more options for the command separated by spaces\&.
+.SH COMMANDS    
+You can specify one of the following commands\&. After the command, specify the options for it\&.
+.TP
+-createbss
+.br
+Converts CSS files into binary form\&.
+.TP
+-createjar
+.br
+Produces a JAR archive according to other parameters\&.
+.TP
+-deploy
+.br
+Assembles the application package for redistribution\&. By default, the deploy task will generate the base application package, but it can also generate a self-contained application package if requested\&.
+.TP
+-makeall
+.br
+Performs compilation, \f3createjar\fR, and \f3deploy\fR steps as one call, with most arguments predefined\&. By default, it attempts to generate all applicable self-contained application packages\&. The source files must be located in a folder called src, and the resulting files (JAR, JNLP, HTML, and self-contained application packages) are put in a folder called dist\&. This command can only be configured in a minimal way and is as automated as possible\&.
+.TP
+-signjar
+.br
+Signs JAR file(s) with a provided certificate\&.
+.SH OPTIONS\ FOR\ THE\ CREATEBSS\ COMMAND    
+.TP
+-outdir \fIdir\fR
+.br
+Name of the directory that will receive generated output files\&.
+.TP
+-srcdir \fIdir\fR
+.br
+Base directory of the files to package\&.
+.TP
+-srcfiles \fIfiles\fR
+.br
+List of files in the directory specified by the \f3-srcdir\fR option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&.
+.SH OPTIONS\ FOR\ THE\ CREATEJAR\ COMMAND    
+.TP
+-appclass \fIapp-class\fR
+.br
+Qualified name of the application class to be executed\&.
+.TP
+-argument \fIarg\fR
+.br
+An unnamed argument to be inserted into the JNLP file as an \f3<fx:argument>\fR element\&.
+.TP
+-classpath \fIfiles\fR
+.br
+List of dependent JAR file names\&.
+.TP
+-manifestAttrs \fImanifest-attributes\fR
+.br
+List of names and values for additional manifest attributes\&. Syntax:
+.sp     
+.nf     
+\f3"name1=value1,name2=value2,name3=value3"\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+
+.TP
+-nocss2bin
+.br
+The packager will not convert CSS files to binary form before copying to JAR\&.
+.TP
+-noembedlauncher
+.br
+If present, the packager will not add the JavaFX launcher classes to the JAR file\&.
+.TP
+-outdir \fIdir\fR
+.br
+Name of the directory that will receive generated output files\&.
+.TP
+-outfile \fIfilename\fR
+.br
+Name (without the extension) of the file that will be generated\&.
+.TP
+-paramfile \fIfile\fR
+.br
+A properties file with default named application parameters\&.
+.TP
+-preloader \fIpreloader-class\fR
+.br
+Qualified name of the preloader class to be executed\&.
+.TP
+-runtimeversion \fIversion\fR
+.br
+Version of the required JavaFX Runtime\&.
+.TP
+-srcdir \fIdir\fR
+.br
+Base directory of the files to package\&.
+.TP
+-srcfiles \fIfiles\fR
+.br
+List of files in the directory specified by the \f3-srcdir\fR option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&.
+.SH OPTIONS\ FOR\ THE\ DEPLOY\ COMMAND    
+.TP
+-allpermissions
+.br
+If present, the application will require all security permissions in the JNLP file\&.
+.TP
+-appclass \fIapp-class\fR
+.br
+Qualified name of the application class to be executed\&.
+.TP
+-argument \fIarg\fR
+.br
+An unnamed argument to be inserted into an \f3<fx:argument>\fR element in the JNLP file\&.
+.TP
+-callbacks
+.br
+Specifies user callback methods in generated HTML\&. The format is the following:
+.sp     
+.nf     
+\f3"name1:value1,name2:value2,\&.\&.\&."\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+
+.TP
+-description \fIdescription\fR
+.br
+Description of the application\&.
+.TP
+-embedCertificates
+.br
+If present, the certificates will be embedded in the JNLP file\&.
+.TP
+-embedjnlp
+.br
+If present, the JNLP file will be embedded in the HTML document\&.
+.TP
+-height \fIheight\fR
+.br
+Height of the application\&.
+.TP
+-htmlparamfile \fIfile\fR
+.br
+Properties file with parameters for the resulting application when it is run in the browser\&.
+.TP
+-isExtension
+.br
+If present, the \f3srcfiles\fR are treated as extensions\&.
+.TP
+-name \fIname\fR
+.br
+Name of the application\&.
+.TP
+-native \fItype\fR
+.br
+Generate self-contained application bundles (if possible)\&. If \fItype\fR is specified, then only a bundle of this type is created\&. List of supported types includes: \f3installer\fR, \f3image\fR, \f3exe\fR, \f3msi\fR, \f3dmg\fR, \f3rpm\fR, \f3deb\fR\&.
+.TP
+-outdir \fIdir\fR
+.br
+Name of the directory that will receive generated output files\&.
+.TP
+-outfile \fIfilename\fR
+.br
+Name (without the extension) of the file that will be generated\&.
+.TP
+-paramfile \fIfile\fR
+.br
+Properties file with default named application parameters\&.
+.TP
+-preloader \fIpreloader-class\fR
+.br
+Qualified name of the preloader class to be executed\&.
+.TP
+-srcdir \fIdir\fR
+.br
+Base directory of the files to package\&.
+.TP
+-srcfiles \fIfiles\fR
+.br
+List of files in the directory specified by the \f3-srcdir\fR option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&.
+.TP
+-templateId
+.br
+Application ID of the application for template processing\&.
+.TP
+-templateInFilename
+.br
+Name of the HTML template file\&. Placeholders are in the following form:
+.sp     
+.nf     
+\f3#XXXX\&.YYYY(APPID)#\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+
+
+Where APPID is the identifier of an application and XXX is one of following:
+.RS     
+.TP 0.2i    
+\(bu
+\f3DT\&.SCRIPT\&.URL\fR
+
+Location of dtjava\&.js in the Deployment Toolkit\&. By default, the location is
+
+http://java\&.com/js/dtjava\&.js
+.TP 0.2i    
+\(bu
+\f3DT\&.SCRIPT\&.CODE\fR
+
+Script element to include dtjava\&.js of the Deployment Toolkit\&.
+.TP 0.2i    
+\(bu
+\f3DT\&.EMBED\&.CODE\&.DYNAMIC\fR
+
+Code to embed the application into a given placeholder\&. It is expected that the code will be wrapped in the \f3function()\fR method\&.
+.TP 0.2i    
+\(bu
+\f3DT\&.EMBED\&.CODE\&.ONLOAD\fR
+
+All the code needed to embed the application into a web page using the \f3onload\fR hook (except inclusion of dtjava\&.js)\&.
+.TP 0.2i    
+\(bu
+\f3DT\&.LAUNCH\&.CODE\fR
+
+Code needed to launch the application\&. It is expected that the code will be wrapped in the \f3function()\fR method\&.
+.RE     
+
+.TP
+-templateOutFilename
+.br
+Name of the HTML file that will be generated from the template\&.
+.TP
+-title \fItitle\fR
+.br
+Title of the application\&.
+.TP
+-vendor \fIvendor\fR
+.br
+Vendor of the application\&.
+.TP
+-width \fIwidth\fR
+.br
+Width of the application\&.
+.TP
+-updatemode \fIupdate-mode\fR
+.br
+Sets the update mode for the JNLP file\&.
+.SH OPTIONS\ FOR\ THE\ MAKEALL\ COMMAND    
+.TP
+-appclass \fIapp-class\fR
+.br
+Qualified name of the application class to be executed\&.
+.TP
+-classpath \fIfiles\fR
+.br
+List of dependent JAR file names\&.
+.TP
+-height \fIheight\fR
+.br
+Height of the application\&.
+.TP
+-name \fIname\fR
+.br
+Name of the application\&.
+.TP
+-preloader \fIpreloader-class\fR
+.br
+Qualified name of the preloader class to be executed\&.
+.TP
+-width \fIwidth\fR
+.br
+Width of the application\&.
+.SH OPTIONS\ FOR\ THE\ SIGNJAR\ COMMAND    
+.TP
+-alias
+.br
+Alias for the key\&.
+.TP
+-keyPass
+.br
+Password for recovering the key\&.
+.TP
+-keyStore \fIfile\fR
+.br
+Keystore file name\&.
+.TP
+-outdir \fIdir\fR
+.br
+Name of the directory that will receive generated output files\&.
+.TP
+-srcdir \fIdir\fR
+.br
+Base directory of the files to be signed\&.
+.TP
+-srcfiles \fIfiles\fR
+.br
+List of files in the directory specified by the \f3-srcdir\fR option\&. If omitted, all files in the directory (which is a mandatory argument in this case) will be used\&. Files in the list must be separated by spaces\&.
+.TP
+-storePass
+.br
+Password to check integrity of the keystore or unlock the keystore
+.TP
+-storeType
+.br
+Keystore type\&. The default value is "jks"\&.
+.SH NOTES    
+.TP 0.2i    
+\(bu
+A \f3-v\fRoption can be used with any task command to enable verbose output\&.
+.TP 0.2i    
+\(bu
+When the \f3-srcdir\fR option is allowed in a command, it can be used more than once\&. If the \f3-srcfiles\fR option is specified, the files named in the argument will be looked for in the location specified in the preceding \f3srcdir\fR option\&. In case there is no \f3-srcdir\fR preceding \f3-srcfiles\fR, the directory where the \f3javafxpackager\fR command is executed will be used\&.
+.SH EXAMPLES    
+\f3Example 1 Using the -createjar Command\fR
+.sp     
+.nf     
+\f3javafxpackager \-createjar \-appclass package\&.ClassName\fP
+.fi     
+.nf     
+\f3  \-srcdir classes \-outdir out \-outfile outjar \-v\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+Packages the contents of the \f3classes\fR directory to \f3outjar\&.jar\fR, sets the application class to \f3package\&.ClassName\fR\&.
+.PP
+\f3Example 2 Using the -deploy Command\fR
+.sp     
+.nf     
+\f3javafxpackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 \fP
+.fi     
+.nf     
+\f3  \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+Generates \f3outfile\&.jnlp\fR and the corresponding \f3outfile\&.html\fR files in \f3outdir\fR for application \f3AppName\fR, which is started by \f3package\&.ClassName\fR and has dimensions of 34 by 43 pixels\&.
+.PP
+\f3Example 3 Using the -makeall Command\fR
+.sp     
+.nf     
+\f3javafxpackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker \-width 600\fP
+.fi     
+.nf     
+\f3\-height 600\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+Does all the packaging work including compilation, \f3createjar\fR, and \f3deploy\fR\&.
+.PP
+\f3Example 4 Using the -signjar Command\fR
+.sp     
+.nf     
+\f3javafxpackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks \-storePass ****\fP
+.fi     
+.nf     
+\f3\-alias javafx \-keypass **** \-srcdir dist\fP
+.fi     
+.nf     
+\f3\fP
+.fi     
+.sp     
+Signs all of the JAR files in the \f3dist\fR directory, attaches a certificate with the specified alias, \f3keyStore\fR and \f3storePass\fR, and puts the signed JAR files back into the \f3dist\fR directory\&.
 .RE
-.\}
-.PP
-where
-\fI\-taskcommand\fR
-is one of the following:
-.PP
-\-createjar
-.RS 4
-Produces a JAR archive according to other parameters\&.
-.RE
-.PP
-\-deploy
-.RS 4
-Assembles the application package for redistribution\&. By default, the deploy task will generate the base application package, but it can also generate a self\-contained application package if requested\&.
-.RE
-.PP
-\-createbss
-.RS 4
-Converts CSS files into binary form\&.
-.RE
-.PP
-\-signJar
-.RS 4
-Signs JAR file(s) with a provided certificate\&.
-.RE
-.PP
-\-makeall
-.RS 4
-Performs compilation,
-\fIcreatejar\fR, and
-\fIdeploy\fR
-steps as one call, with most arguments predefined\&. By default, it attempts to generate all applicable self\-contained application packages\&. The source files must be located in a folder called src, and the resulting files (JAR, JNLP, HTML, and self\-contained application packages) are put in a folder called dist\&. This command can only be configured in a minimal way and is as automated as possible\&.
-.RE
-.PP
-Note that all options are case\-insensitive\&.
-.SH "OPTIONS FOR THE CREATEJAR COMMAND"
-.PP
-\-appclass \fI<application class>\fR
-.RS 4
-Qualified name of the application class to be executed\&.
-.RE
-.PP
-\-preloader \fI<preloader class>\fR
-.RS 4
-Qualified name of the preloader class to be executed\&.
-.RE
-.PP
-\-paramfile <file>
-.RS 4
-A properties file with default named application parameters\&.
-.RE
-.PP
-\-argument arg
-.RS 4
-An unnamed argument to be inserted into the JNLP file as an
-\fI<fx:argument>\fR
-element\&.
-.RE
-.PP
-\-classpath \fI<files>\fR
-.RS 4
-List of dependent JAR file names\&.
-.RE
-.PP
-\-manifestAttrs \fI<manifest attributes>\fR
-.RS 4
-List of additional manifest attributes\&. Syntax:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-"name1=value1,name2=value2,name3=value3"
-.fi
-.if n \{\
-.RE
-.\}
-.RE
-.PP
-\-noembedlauncher
-.RS 4
-If present, the packager will not add the JavaFX launcher classes to the JAR file\&.
-.RE
-.PP
-\-nocss2bin
-.RS 4
-The packager will not convert CSS files to binary form before copying to JAR\&.
-.RE
-.PP
-\-runtimeversion \fI<version>\fR
-.RS 4
-Version of the required JavaFX Runtime\&.
-.RE
-.PP
-\-outdir \fI<dir>\fR
-.RS 4
-Name of the directory that will receive generated output files\&.
-.RE
-.PP
-\-outfile \fI<filename>\fR
-.RS 4
-Name (without the extension) of the file that will be generated\&.
-.RE
-.PP
-\-srcdir \fI<dir>\fR
-.RS 4
-Base directory of the files to package\&.
-.RE
-.PP
-\-srcfiles \fI<files>\fR
-.RS 4
-List of files in
-\fIsrcdir\fR\&. If omitted, all files in
-\fIsrcdir\fR
-(which is a mandatory argument in this case) will be used\&.
-.RE
-.SH "OPTIONS FOR THE DEPLOY COMMAND"
-.PP
-\-title \fI<title>\fR
-.RS 4
-Title of the application\&.
-.RE
-.PP
-\-vendor \fI<vendor>\fR
-.RS 4
-Vendor of the application\&.
-.RE
-.PP
-\-description \fI<description>\fR
-.RS 4
-Description of the application\&.
-.RE
-.PP
-\-appclass \fI<application class>\fR
-.RS 4
-Qualified name of the application class to be executed\&.
-.RE
-.PP
-\-preloader \fI<preloader class>\fR
-.RS 4
-Qualified name of the preloader class to be executed\&.
-.RE
-.PP
-\-paramfile \fI<file>\fR
-.RS 4
-Properties file with default named application parameters\&.
-.RE
-.PP
-\-htmlparamfile \fI<file>\fR
-.RS 4
-Properties file with parameters for the resulting application when it is run in the browser\&.
-.RE
-.PP
-\-width \fI<width>\fR
-.RS 4
-Width of the application\&.
-.RE
-.PP
-\-height \fI<height>\fR
-.RS 4
-Height of the application\&.
-.RE
-.PP
-\-native \fI<type>\fR
-.RS 4
-Generate self\-contained application bundles (if possible)\&. If
-\fItype\fR
-is specified, then only a bundle of this type is created\&. List of supported types includes: installer, image, exe, msi, dmg, rpm, deb\&.
-.RE
-.PP
-\-name \fI<name>\fR
-.RS 4
-Name of the application\&.
-.RE
-.PP
-\-embedjnlp
-.RS 4
-If present, the JNLP file will be embedded in the HTML document\&.
-.RE
-.PP
-\-embedCertificates
-.RS 4
-If present, the certificates will be embedded in the JNLP file\&.
-.RE
-.PP
-\-allpermissions
-.RS 4
-If present, the application will require all security permissions in the JNLP file\&.
-.RE
-.PP
-\-updatemode \fI<updatemode>\fR
-.RS 4
-Sets the update mode for the JNLP file\&.
-.RE
-.PP
-\-isExtension
-.RS 4
-If present, the
-\fIsrcfiles\fR
-are treated as extensions\&.
-.RE
-.PP
-\-callbacks
-.RS 4
-Specifies user callback methods in generated HTML\&. The format is the following:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-"name1:value1,name2:value2,\&.\&.\&."
-.fi
-.if n \{\
-.RE
-.\}
-.RE
-.PP
-\-templateInFilename
-.RS 4
-Name of the HTML template file\&. Placeholders are in the following form:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-#XXXX\&.YYYY(APPID)#
-.fi
-.if n \{\
-.RE
-.\}
-.RE
-.PP
-\-templateOutFilename
-.RS 4
-Name of the HTML file that will be generated from the template\&.
-.RE
-.PP
-\-templateId
-.RS 4
-Application ID of the application for template processing\&.
-.RE
-.PP
-\-argument arg
-.RS 4
-An unnamed argument to be inserted into an
-\fI<fx:argument>\fR
-element in the JNLP file\&.
-.RE
-.PP
-\-outdir \fI<dir>\fR
-.RS 4
-Name of the directory that will receive generated output files\&.
-.RE
-.PP
-\-outfile \fI<filename>\fR
-.RS 4
-Name (without the extension) of the file that will be generated\&.
-.RE
-.PP
-\-srcdir \fI<dir>\fR
-.RS 4
-Base directory of the files to package\&.
-.RE
-.PP
-\-srcfiles \fI<files>\fR
-.RS 4
-List of files in
-\fIsrcdir\fR\&. If omitted, all files in
-\fIsrcdir\fR
-(which is a mandatory argument in this case) will be used\&.
-.RE
-.SH "OPTIONS FOR THE CREATEBSS COMMAND"
-.PP
-\-outdir \fI<dir>\fR
-.RS 4
-Name of the directory that will receive generated output files\&.
-.RE
-.PP
-\-srcdir \fI<dir>\fR
-.RS 4
-Base directory of the files to package\&.
-.RE
-.PP
-\-srcfiles \fI<files>\fR
-.RS 4
-List of files in
-\fIsrcdir\fR\&. If omitted, all files in
-\fIsrcdir\fR
-(which is a mandatory argument in this case) will be used\&.
-.RE
-.SH "OPTIONS FOR THE SIGNJAR COMMAND"
-.PP
-\-keyStore \fI<file>\fR
-.RS 4
-Keystore file name\&.
-.RE
-.PP
-\-alias
-.RS 4
-Alias for the key\&.
-.RE
-.PP
-\-storePass
-.RS 4
-Password to check integrity of the keystore or unlock the keystore
-.RE
-.PP
-\-keyPass
-.RS 4
-Password for recovering the key\&.
-.RE
-.PP
-\-storeType
-.RS 4
-Keystore type\&. The default value is "jks"\&.
-.RE
-.PP
-\-outdir \fI<dir>\fR
-.RS 4
-Name of the directory that will receive generated output files\&.
-.RE
-.PP
-\-srcdir \fI<dir>\fR
-.RS 4
-Base directory of the files to be signed\&.
-.RE
-.PP
-\-srcfiles \fI<files>\fR
-.RS 4
-List of files in
-\fIsrcdir\fR\&. If omitted, all files in
-\fIsrcdir\fR
-(which is a mandatory argument in this case) will be used\&.
-.RE
-.SH "OPTIONS FOR THE MAKEALL COMMAND"
-.PP
-\-appclass \fI<application class>\fR
-.RS 4
-Qualified name of the application class to be executed\&.
-.RE
-.PP
-\-preloader \fI<preloader class>\fR
-.RS 4
-Qualified name of the preloader class to be executed\&.
-.RE
-.PP
-\-classpath \fI<files>\fR
-.RS 4
-List of dependent JAR file names\&.
-.RE
-.PP
-\-name \fI<name>\fR
-.RS 4
-Name of the application\&.
-.RE
-.PP
-\-width \fI<width>\fR
-.RS 4
-Width of the application\&.
-.RE
-.PP
-\-height \fI<height>\fR
-.RS 4
-Height of the application\&.
-.RE
-.SH "NOTES"
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
-A
-\fI\-v \fRoption can be used with any task command to enable verbose output\&.
-.RE
-.sp
-.RS 4
-.ie n \{\
-\h'-04'\(bu\h'+03'\c
-.\}
-.el \{\
-.sp -1
-.IP \(bu 2.3
-.\}
-When the
-\fI\-srcdir\fR
-option is allowed in a command, it can be used more than once\&. If the
-\fI\-srcfiles\fR
-option is specified, the files named in the argument will be looked for in the location specified in the preceding
-\fIsrcdir\fR
-option\&. In case there is no
-\fI\-srcdir\fR
-preceding
-\fI\-srcfiles\fR, the directory where the javafxpackager command is executed will be used\&.
-.RE
-.SH "EXAMPLES"
-.PP
-\fBExample 1\fR, \-createjar Command Usage
-.RS 4
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-javafxpackager \-createjar \-appclass package\&.ClassName
-  \-srcdir classes \-outdir out \-outfile outjar \-v
-.fi
-.if n \{\
-.RE
-.\}
-Packages the contents of the classes directory to outjar\&.jar, sets the application class to package\&.ClassName\&.
-.RE
-.PP
-\fBExample 2\fR, \-deploy Command Usage
-.RS 4
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-javafxpackager \-deploy \-outdir outdir \-outfile outfile \-width 34 \-height 43 
-  \-name AppName \-appclass package\&.ClassName \-v \-srcdir compiled
-.fi
-.if n \{\
-.RE
-.\}
-Generates outfile\&.jnlp and the corresponding outfile\&.html files in outdir for application AppName, which is started by package\&.ClassName and has dimensions of 34 x 43\&.
-.RE
-.PP
-\fBExample 3\fR, \-makeall command Usage
-.RS 4
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-javafxpackager \-makeall \-appclass brickbreaker\&.Main \-name BrickBreaker
-  \-width 600 \-height 600
-.fi
-.if n \{\
-.RE
-.\}
-Does all the packaging work including compilation: compile, createjar, deploy\&.
-.RE
-.PP
-\fBExample 4\fR, \-signJar Command Usage
-.RS 4
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-javafxpackager \-signJar \-\-outdir dist \-keyStore sampleKeystore\&.jks 
-.fi
-.if n \{\
-.RE
-.\}
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-    \-storePass **** \-alias javafx \-keypass **** \-srcdir dist
-.fi
-.if n \{\
-.RE
-.\}
-Signs all of the JAR files in the dist directory, attaches a certificate with the specified alias, keyStore and storePass, and puts the signed JAR files back into the dist directory\&.
-.RE
+.br
+'pl 8.5i
+'bp