42 \ -p modulePath -m moduleName/className\n\
43 \ To provide your own options to jlink, run jlink separately:\n\
44 \ jlink --output appRuntimeImage -p ModulePath -m moduleName\\\n\
45 \ --no-header-files [<additional jlink options>...]\n\
46 \ jpackage create-app-image -o outputdir -n name\\\n\
47 \ -m moduleName/className --runtime-image appRuntimeIMage\n\
48 \ Generate an application installer:\n\
49 \ jpackage create-installer -o outputdir -n name \\\n\
50 \ -p modulePath -m moduleName/className\n\
51 \ jpackage create-installer -i inputdir -o outputdir -n name \\\n\
52 \ --main-class package.ClassName --main-jar MyJar.jar\n\
53 \ jpackage create-installer -o outputdir -n <installer-name> \\\n\
54 \ --app-image <app image dir> [--installer-type <type>]\n\
55 \ Generate a Java runtime installer:\n\
56 \ jpackage create-installer -o outputdir -n name \\\n\
57 \ --runtime-image <runtime-image>\n\
58 \n\
59 Generic Options:\n\
60 \ @<filename> \n\
61 \ Read options and/or mode from a file \n\
62 \ --app-version <version>\n\
63 \ Version of the application and/or installer\n\
64 \ --copyright <copyright string>\n\
65 \ Copyright for the application\n\
66 \ --description <description string>\n\
67 \ Description of the application\n\
68 \ --help -h \n\
69 \ Print the usage text with a list and description of each valid\n\
70 \ option for the current platform to the output stream, and exit\n\
71 \ --name -n <name>\n\
72 \ Name of the application and/or installer\n\
73 \ --output -o <output path>\n\
74 \ Path where generated output file is placed\n\
75 \ (absolute path or relative to the current directory)\n\
76 \ --temp-root <file path>\n\
77 \ Path of a new or empty directory used to create temporary files\n\
78 \ (absolute path or relative to the current directory)\n\
79 \ If specified, the temp-root will not be removed upon the task\n\
80 \ completion and must be removed manually\n\
81 \ If not specified, a temporary directory will be created and\n\
82 \ removed upon the task completion.\n\
83 \ --vendor <vendor string>\n\
84 \ Vendor of the application\n\
85 \ --verbose\n\
86 \ Enables verbose output\n\
87 \ --version\n\
88 \ Print the product version to the output stream and exit\n\
89 \n\
90 \Options for creating the runtime image:\n\
91 \ --add-modules <module name>[,<module name>...]\n\
92 \ A comma (",") separated list of modules to add.\n\
93 \ This module list, along with the main module (if specified)\n\
94 \ will be passed to jlink as the --add-module argument.\n\
95 \ if not specified, either just the main module (if --module is\n\
96 \ specified), or the default set of modules (if --main-jar is \n\
97 \ specified) are used.\n\
98 \ --module-path -p <module path>...\n\
99 \ A {0} separated list of paths\n\
100 \ Each path is either a directory of modules or the path to a\n\
101 \ modular jar.\n\
102 \ (each path is absolute or relative to the current directory)\n\
103 \ --runtime-image <file path>\n\
104 \ Path of the predefined runtime image that will be copied into\n\
105 \ the application image\n\
106 \ (absolute path or relative to the current directory)\n\
107 \ If --runtime-image is not specified, jpackage will run jlink to\n\
108 \ create the runtime image using options:\n\
109 \ --strip-debug, --no-header-files, --no-man-pages, and\n\
110 \ --strip-native-commands. --bind-services will also be added if\n\
111 \ --add-modules is not specified.\n\
112 \n\
113 \Options for creating the application image:\n\
114 \ --icon <icon file path>\n\
115 \ Path of the icon of the application bundle\n\
116 \ (absolute path or relative to the current directory)\n\
117 \ --input -i <input path>\n\
118 \ Path of the input directory that contains the files to be packaged\n\
119 \ (absolute path or relative to the current directory)\n\
120 \ All files in the input directory will be packaged into the\n\
121 \ application image.\n\
122 \n\
123 \Options for creating the application launcher(s):\n\
124 \ --add-launcher <file path>\n\
125 \ Path to a Properties file that contains list of key, value pairs\n\
126 \ (absolute path or relative to the current directory)\n\
127 \ The keys "name" (required), "module", "add-modules",\n\
128 \ "main-jar", "main-class", "arguments", "java-options",\n\
129 \ "app-version", "icon", and "win-console" can be used.\n\
130 \ These options are added to, or used to overwrite, the original\n\
131 \ command line options to build an additional alternative launcher.\n\
132 \ The main application launcher will be built from the command line\n\
133 \ options. Additional alternative launchers may be built using\n\
134 \ this option.\n\
135 \ --arguments <main class arguments>\n\
136 \ Command line arguments to pass to the main class if no command\n\
137 \ line arguments are given to the launcher\n\
138 \ --java-options <java options>\n\
139 \ Options to pass to the Java runtime\n\
140 \ --main-class <class name>\n\
141 \ Qualified name of the application main class to execute\n\
142 \ This option can only be used if --main-jar is specified.\n\
143 \ --main-jar <main jar file>\n\
144 \ The main JAR of the application; containing the main class\n\
145 \ (specified as a path relative to the input path)\n\
146 \ Either --module or --main-jar option can be specified but not\n\
147 \ both.\n\
148 \ --module -m <module name>[/<main class>]\n\
149 \ The main module (and optionally main class) of the application\n\
150 \ This module must be located on the module path.\n\
151 \ When this option is specified, the main module will be linked\n\
152 \ in the Java runtime image. Either --module or --main-jar\n\
153 \ option can be specified but not both.\n\
154 {2}\n\
155 \Options for creating the application installer(s):\n\
156 \ --app-image <file path>\n\
157 \ Location of the predefined application image that is used\n\
158 \ to build an installable package\n\
159 \ (absolute path or relative to the current directory)\n\
160 \ See create-app-image mode options to create the application image.\n\
161 \ --file-associations <file path>\n\
162 \ Path to a Properties file that contains list of key, value pairs\n\
163 \ (absolute path or relative to the current directory)\n\
164 \ The keys "extension", "mime-type", "icon", and "description"\n\
165 \ can be used to describe the association.\n\
166 \ --identifier <id string>\n\
167 \ An identifier that uniquely identifies the application\n\
168 \ Defaults to the main class name.\n\
169 \ The value should be a valid DNS name.\n\
170 \ --install-dir <file path>\n\
171 \ {4}\
172 \ --installer-type <type> \n\
173 \ The type of the installer to create\n\
174 \ Valid values are: {1} \n\
175 \ If this option is not specified (in create-installer mode) all\n\
176 \ supported types of installable packages for the current\n\
177 \ platform will be created.\n\
178 \ --license-file <file path>\n\
179 \ Path to the license file\n\
180 \ (absolute path or relative to the current directory)\n\
181 \ --resource-dir <path>\n\
182 \ Path to override jpackage resources\n\
183 \ Icons, template files, and other resources of jpackage can be\n\
184 \ over-ridden by adding replacement resources to this directory.\n\
185 \ (absolute path or relative to the current directory)\n\
|
42 \ -p modulePath -m moduleName/className\n\
43 \ To provide your own options to jlink, run jlink separately:\n\
44 \ jlink --output appRuntimeImage -p ModulePath -m moduleName\\\n\
45 \ --no-header-files [<additional jlink options>...]\n\
46 \ jpackage create-app-image -o outputdir -n name\\\n\
47 \ -m moduleName/className --runtime-image appRuntimeIMage\n\
48 \ Generate an application installer:\n\
49 \ jpackage create-installer -o outputdir -n name \\\n\
50 \ -p modulePath -m moduleName/className\n\
51 \ jpackage create-installer -i inputdir -o outputdir -n name \\\n\
52 \ --main-class package.ClassName --main-jar MyJar.jar\n\
53 \ jpackage create-installer -o outputdir -n <installer-name> \\\n\
54 \ --app-image <app image dir> [--installer-type <type>]\n\
55 \ Generate a Java runtime installer:\n\
56 \ jpackage create-installer -o outputdir -n name \\\n\
57 \ --runtime-image <runtime-image>\n\
58 \n\
59 Generic Options:\n\
60 \ @<filename> \n\
61 \ Read options and/or mode from a file \n\
62 \ This Option can be used Multiple times.\n\
63 \ --app-version <version>\n\
64 \ Version of the application and/or installer\n\
65 \ --copyright <copyright string>\n\
66 \ Copyright for the application\n\
67 \ --description <description string>\n\
68 \ Description of the application\n\
69 \ --help -h \n\
70 \ Print the usage text with a list and description of each valid\n\
71 \ option for the current platform to the output stream, and exit\n\
72 \ --name -n <name>\n\
73 \ Name of the application and/or installer\n\
74 \ --output -o <output path>\n\
75 \ Path where generated output file is placed\n\
76 \ (absolute path or relative to the current directory)\n\
77 \ --temp-root <file path>\n\
78 \ Path of a new or empty directory used to create temporary files\n\
79 \ (absolute path or relative to the current directory)\n\
80 \ If specified, the temp-root will not be removed upon the task\n\
81 \ completion and must be removed manually\n\
82 \ If not specified, a temporary directory will be created and\n\
83 \ removed upon the task completion.\n\
84 \ --vendor <vendor string>\n\
85 \ Vendor of the application\n\
86 \ --verbose\n\
87 \ Enables verbose output\n\
88 \ --version\n\
89 \ Print the product version to the output stream and exit\n\
90 \n\
91 \Options for creating the runtime image:\n\
92 \ --add-modules <module name>[,<module name>...]\n\
93 \ A comma (",") separated list of modules to add.\n\
94 \ This module list, along with the main module (if specified)\n\
95 \ will be passed to jlink as the --add-module argument.\n\
96 \ if not specified, either just the main module (if --module is\n\
97 \ specified), or the default set of modules (if --main-jar is \n\
98 \ specified) are used.\n\
99 \ This Option can be used Multiple times.\n\
100 \ --module-path -p <module path>...\n\
101 \ A {0} separated list of paths\n\
102 \ Each path is either a directory of modules or the path to a\n\
103 \ modular jar.\n\
104 \ (each path is absolute or relative to the current directory)\n\
105 \ This Option can be used Multiple times.\n\
106 \ --runtime-image <file path>\n\
107 \ Path of the predefined runtime image that will be copied into\n\
108 \ the application image\n\
109 \ (absolute path or relative to the current directory)\n\
110 \ If --runtime-image is not specified, jpackage will run jlink to\n\
111 \ create the runtime image using options:\n\
112 \ --strip-debug, --no-header-files, --no-man-pages, and\n\
113 \ --strip-native-commands. --bind-services will also be added if\n\
114 \ --add-modules is not specified.\n\
115 \n\
116 \Options for creating the application image:\n\
117 \ --icon <icon file path>\n\
118 \ Path of the icon of the application bundle\n\
119 \ (absolute path or relative to the current directory)\n\
120 \ --input -i <input path>\n\
121 \ Path of the input directory that contains the files to be packaged\n\
122 \ (absolute path or relative to the current directory)\n\
123 \ All files in the input directory will be packaged into the\n\
124 \ application image.\n\
125 \n\
126 \Options for creating the application launcher(s):\n\
127 \ --add-launcher <launcher name>=<file path>\n\
128 \ Name of launcher, and a path to a Properties file that contains\n\
129 \ a list of key, value pairs\n\
130 \ (absolute path or relative to the current directory)\n\
131 \ The keys "module", "add-modules", "main-jar", "main-class",\n\
132 \ "arguments", "java-options", "app-version", "icon", and\n\
133 \ "win-console" can be used.\n\
134 \ These options are added to, or used to overwrite, the original\n\
135 \ command line options to build an additional alternative launcher.\n\
136 \ The main application launcher will be built from the command line\n\
137 \ options. Additional alternative launchers can be built using\n\
138 \ this option, and this option can be used multiple times to\n\
139 \ build multiple additional launchers. \n\
140 \ --arguments <main class arguments>\n\
141 \ Command line arguments to pass to the main class if no command\n\
142 \ line arguments are given to the launcher\n\
143 \ This Option can be used Multiple times.\n\
144 \ --java-options <java options>\n\
145 \ Options to pass to the Java runtime\n\
146 \ This Option can be used Multiple times.\n\
147 \ --main-class <class name>\n\
148 \ Qualified name of the application main class to execute\n\
149 \ This option can only be used if --main-jar is specified.\n\
150 \ --main-jar <main jar file>\n\
151 \ The main JAR of the application; containing the main class\n\
152 \ (specified as a path relative to the input path)\n\
153 \ Either --module or --main-jar option can be specified but not\n\
154 \ both.\n\
155 \ --module -m <module name>[/<main class>]\n\
156 \ The main module (and optionally main class) of the application\n\
157 \ This module must be located on the module path.\n\
158 \ When this option is specified, the main module will be linked\n\
159 \ in the Java runtime image. Either --module or --main-jar\n\
160 \ option can be specified but not both.\n\
161 {2}\n\
162 \Options for creating the application installer(s):\n\
163 \ --app-image <file path>\n\
164 \ Location of the predefined application image that is used\n\
165 \ to build an installable package\n\
166 \ (absolute path or relative to the current directory)\n\
167 \ See create-app-image mode options to create the application image.\n\
168 \ --file-associations <file path>\n\
169 \ Path to a Properties file that contains list of key, value pairs\n\
170 \ (absolute path or relative to the current directory)\n\
171 \ The keys "extension", "mime-type", "icon", and "description"\n\
172 \ can be used to describe the association.\n\
173 \ This Option can be used Multiple times.\n\
174 \ --identifier <id string>\n\
175 \ An identifier that uniquely identifies the application\n\
176 \ Defaults to the main class name.\n\
177 \ The value should be a valid DNS name.\n\
178 \ --install-dir <file path>\n\
179 \ {4}\
180 \ --installer-type <type> \n\
181 \ The type of the installer to create\n\
182 \ Valid values are: {1} \n\
183 \ If this option is not specified (in create-installer mode) all\n\
184 \ supported types of installable packages for the current\n\
185 \ platform will be created.\n\
186 \ --license-file <file path>\n\
187 \ Path to the license file\n\
188 \ (absolute path or relative to the current directory)\n\
189 \ --resource-dir <path>\n\
190 \ Path to override jpackage resources\n\
191 \ Icons, template files, and other resources of jpackage can be\n\
192 \ over-ridden by adding replacement resources to this directory.\n\
193 \ (absolute path or relative to the current directory)\n\
|