7 # published by the Free Software Foundation. Oracle designates this 8 # particular file as subject to the "Classpath" exception as provided 9 # by Oracle in the LICENSE file that accompanied this code. 10 # 11 # This code is distributed in the hope that it will be useful, but WITHOUT 12 # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 13 # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 14 # version 2 for more details (a copy is included in the LICENSE file that 15 # accompanied this code). 16 # 17 # You should have received a copy of the GNU General Public License version 18 # 2 along with this work; if not, write to the Free Software Foundation, 19 # Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 20 # 21 # Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 22 # or visit www.oracle.com if you need additional information or have any 23 # questions. 24 # 25 # 26 27 MSG_Help=Usage: jpackage <mode> <options>\n\ 28 \n\ 29 where mode is one of: \n\ 30 \ create-app-image\n\ 31 \ Generates a platform-specific application image.\n\ 32 \ create-installer\n\ 33 \ Generates a platform-specific installer for the application.\n\ 34 \ \n\ 35 Sample usages:\n\ 36 --------------\n\ 37 \ Generate a non-modular application image:\n\ 38 \ jpackage create-app-image -o outputdir -i inputdir -n name \\\n\ 39 \ --main-class className --main-jar MyJar.jar\n\ 40 \ Generate a modular application image:\n\ 41 \ jpackage create-app-image -o outputdir -n name \\\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\ 194 \ --runtime-image <file-path>\n\ 195 \ Path of the predefined runtime image to install\n\ 196 \ (absolute path or relative to the current directory)\n\ 197 \ Option is required when creating a runtime installer.\n\ 198 \n\ 199 \Platform dependent options for creating the application installer(s):\n\ 200 {3} 201 202 MSG_Help_win_launcher=\ 203 \n\ 204 \Platform dependent option for creating the application launcher:\n\ 205 \ --win-console\n\ 206 \ Creates a console launcher for the application, should be\n\ 207 \ specified for application which requires console interactions\n\ 208 209 MSG_Help_win_install=\ 210 \ --win-dir-chooser\n\ 211 \ Adds a dialog to enable the user to choose a directory in which\n\ 212 \ the product is installed\n\ 213 \ --win-menu\n\ 214 \ Adds the application to the system menu\n\ 215 \ --win-menu-group <menu group name>\n\ 216 \ Start Menu group this application is placed in\n\ 217 \ --win-per-user-install\n\ 218 \ Request to perform an install on a per-user basis\n\ 219 \ --win-registry-name <registry name>\n\ 220 \ Name of the application for registry references.\n\ 221 \ The default is the Application Name with only\n\ 222 \ alphanumerics, dots, and dashes (no whitespace)\n\ 223 \ --win-shortcut\n\ 224 \ Creates a desktop shortcut for the application\n\ 225 \ --win-upgrade-uuid <id string>\n\ 226 \ UUID associated with upgrades for this package\n\ 227 228 MSG_Help_win_install_dir=\ 229 \Relative sub-path under the default installation location\n\ 230 231 MSG_Help_mac_launcher=\ 232 \ --mac-bundle-identifier <ID string>\n\ 233 \ An identifier that uniquely identifies the application for MacOSX\n\ 234 \ Defaults to the value of --identifier option.\n\ 235 \ May only use alphanumeric (A-Z,a-z,0-9), hyphen (-),\n\ 236 \ and period (.) characters.\n\ 237 \ --mac-bundle-name <name string>\n\ 238 \ Name of the application as it appears in the Menu Bar\n\ 239 \ This can be different from the application name.\n\ 240 \ This name must be less than 16 characters long and be suitable for\n\ 241 \ displaying in the menu bar and the application Info window.\n\ 242 \ Defaults to the application name.\n\ 243 \ --mac-bundle-signing-prefix <prefix string>\n\ 244 \ When signing the application bundle, this value is prefixed to all\n\ 245 \ components that need to be signed that don't have\n\ 246 \ an existing bundle identifier.\n\ 247 \ --mac-sign\n\ 248 \ Request that the bundle be signed\n\ 249 \ --mac-signing-keychain <file path>\n\ 250 \ Path of the keychain to use\n\ 251 \ (absolute path or relative to the current directory)\n\ 252 \ If not specified, the standard keychains are used.\n\ 253 \ --mac-signing-key-user-name <user name>\n\ 254 \ User name portion of the typical\n\ 255 \ "Mac Developer ID Application: <user name>" signing key\n\ 256 257 MSG_Help_linux_install=\ 258 \ --linux-bundle-name <bundle name>\n\ 259 \ Name for Linux bundle, defaults to the application name\n\ 260 \ --linux-deb-maintainer <email address>\n\ 261 \ Maintainer for .deb bundle\n\ 262 \ --linux-menu-group <menu-group-name>\n\ 263 \ Menu group this application is placed in\n\ 264 \ --linux-package-deps\n\ 265 \ Required packages or capabilities for the application\n\ 266 \ --linux-rpm-license-type <type string>\n\ 267 \ Type of the license ("License: <value>" of the RPM .spec)\n\ 268 269 MSG_Help_mac_linux_install_dir=\ 270 \Absolute path of the installation directory of the application\n\ 271 272 MSG_Help_default_install_dir=\ 273 \Absolute path of the installation directory of the application on OS X\n\ 274 \ or Linux. Relative sub-path of the installation location of the application\n\ 275 \ such as "Program Files" or "AppData" on Windows.\n\ 276 277 MSG_Help_no_args=Usage: jpackage <mode> <options>\n\ 278 \Use jpackage --help (or -h) for a list of possible options\ 279 | 7 # published by the Free Software Foundation. Oracle designates this 8 # particular file as subject to the "Classpath" exception as provided 9 # by Oracle in the LICENSE file that accompanied this code. 10 # 11 # This code is distributed in the hope that it will be useful, but WITHOUT 12 # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or 13 # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License 14 # version 2 for more details (a copy is included in the LICENSE file that 15 # accompanied this code). 16 # 17 # You should have received a copy of the GNU General Public License version 18 # 2 along with this work; if not, write to the Free Software Foundation, 19 # Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. 20 # 21 # Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA 22 # or visit www.oracle.com if you need additional information or have any 23 # questions. 24 # 25 # 26 27 MSG_Help=Usage: jpackage <options>\n\ 28 \n\ 29 Sample usages:\n\ 30 --------------\n\ 31 \ Generate an application package suitable for the host system:\n\ 32 \ For a modular application:\n\ 33 \ jpackage -n name -p modulePath -m moduleName/className\n\ 34 \ For a non-modular application:\n\ 35 \ jpackage -i inputDir -n name \\\n\ 36 \ --main-class className --main-jar myJar.jar\n\ 37 \ From a pre-built application image:\n\ 38 \ jpackage -n name --app-image appImageDir\n\ 39 \ Generate an application image:\n\ 40 \ For a modular application:\n\ 41 \ jpackage --type app-image -n name -p modulePath \\\n\ 42 \ -m moduleName/className\n\ 43 \ For a non-modular application:\n\ 44 \ jpackage --type app-image -i inputDir -n name \\\n\ 45 \ --main-class className --main-jar myJar.jar\n\ 46 \ To provide your own options to jlink, run jlink separately:\n\ 47 \ jlink --output appRuntimeImage -p modulePath -m moduleName \\\n\ 48 \ --no-header-files [<additional jlink options>...]\n\ 49 \ jpackage --type app-image -n name \\\n\ 50 \ -m moduleName/className --runtime-image appRuntimeImage\n\ 51 \ Generate a Java runtime package:\n\ 52 \ jpackage -n name --runtime-image <runtime-image>\n\ 53 \n\ 54 Generic Options:\n\ 55 \ @<filename> \n\ 56 \ Read options and/or mode from a file \n\ 57 \ This option can be used multiple times.\n\ 58 \ --type -t <type> \n\ 59 \ The type of package to create\n\ 60 \ Valid values are: {1} \n\ 61 \ If this option is not specified a platform dependent\n\ 62 \ default type will be created.\n\ 63 \ --app-version <version>\n\ 64 \ Version of the application and/or package\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 package\n\ 74 \ --dest -d <destination path>\n\ 75 \ Path where generated output file is placed\n\ 76 \ Defaults to the current working directory.\n\ 77 \ (absolute path or relative to the current directory)\n\ 78 \ --temp <file path>\n\ 79 \ Path of a new or empty directory used to create temporary files\n\ 80 \ (absolute path or relative to the current directory)\n\ 81 \ If specified, the temp dir will not be removed upon the task\n\ 82 \ completion and must be removed manually\n\ 83 \ If not specified, a temporary directory will be created and\n\ 84 \ removed upon the task completion.\n\ 85 \ --vendor <vendor string>\n\ 86 \ Vendor of the application\n\ 87 \ --verbose\n\ 88 \ Enables verbose output\n\ 89 \ --version\n\ 90 \ Print the product version to the output stream and exit\n\ 91 \n\ 92 \Options for creating the runtime image:\n\ 93 \ --add-modules <module name>[,<module name>...]\n\ 94 \ A comma (",") separated list of modules to add.\n\ 95 \ This module list, along with the main module (if specified)\n\ 96 \ will be passed to jlink as the --add-module argument.\n\ 97 \ if not specified, either just the main module (if --module is\n\ 98 \ specified), or the default set of modules (if --main-jar is \n\ 99 \ specified) are used.\n\ 100 \ This option can be used multiple times.\n\ 101 \ --module-path -p <module path>...\n\ 102 \ A {0} separated list of paths\n\ 103 \ Each path is either a directory of modules or the path to a\n\ 104 \ modular jar.\n\ 105 \ (each path is absolute or relative to the current directory)\n\ 106 \ This option can be used multiple times.\n\ 107 \ --bind-services \n\ 108 \ Pass on --bind-services option to jlink (which will link in \n\ 109 \ service provider modules and their dependences) \n\ 110 \ --runtime-image <file path>\n\ 111 \ Path of the predefined runtime image that will be copied into\n\ 112 \ the application image\n\ 113 \ (absolute path or relative to the current directory)\n\ 114 \ If --runtime-image is not specified, jpackage will run jlink to\n\ 115 \ create the runtime image using options:\n\ 116 \ --strip-debug, --no-header-files, --no-man-pages, and\n\ 117 \ --strip-native-commands.\n\ 118 \n\ 119 \Options for creating the application image:\n\ 120 \ --icon <icon file path>\n\ 121 \ Path of the icon of the application package\n\ 122 \ (absolute path or relative to the current directory)\n\ 123 \ --input -i <input path>\n\ 124 \ Path of the input directory that contains the files to be packaged\n\ 125 \ (absolute path or relative to the current directory)\n\ 126 \ All files in the input directory will be packaged into the\n\ 127 \ application image.\n\ 128 \n\ 129 \Options for creating the application launcher(s):\n\ 130 \ --add-launcher <launcher name>=<file path>\n\ 131 \ Name of launcher, and a path to a Properties file that contains\n\ 132 \ a list of key, value pairs\n\ 133 \ (absolute path or relative to the current directory)\n\ 134 \ The keys "module", "main-jar", "main-class",\n\ 135 \ "arguments", "java-options", "app-version", "icon", and\n\ 136 \ "win-console" can be used.\n\ 137 \ These options are added to, or used to overwrite, the original\n\ 138 \ command line options to build an additional alternative launcher.\n\ 139 \ The main application launcher will be built from the command line\n\ 140 \ options. Additional alternative launchers can be built using\n\ 141 \ this option, and this option can be used multiple times to\n\ 142 \ build multiple additional launchers. \n\ 143 \ --arguments <main class arguments>\n\ 144 \ Command line arguments to pass to the main class if no command\n\ 145 \ line arguments are given to the launcher\n\ 146 \ This option can be used multiple times.\n\ 147 \ --java-options <java options>\n\ 148 \ Options to pass to the Java runtime\n\ 149 \ This option can be used multiple times.\n\ 150 \ --main-class <class name>\n\ 151 \ Qualified name of the application main class to execute\n\ 152 \ This option can only be used if --main-jar is specified.\n\ 153 \ --main-jar <main jar file>\n\ 154 \ The main JAR of the application; containing the main class\n\ 155 \ (specified as a path relative to the input path)\n\ 156 \ Either --module or --main-jar option can be specified but not\n\ 157 \ both.\n\ 158 \ --module -m <module name>[/<main class>]\n\ 159 \ The main module (and optionally main class) of the application\n\ 160 \ This module must be located on the module path.\n\ 161 \ When this option is specified, the main module will be linked\n\ 162 \ in the Java runtime image. Either --module or --main-jar\n\ 163 \ option can be specified but not both.\n\ 164 {2}\n\ 165 \Options for creating the application package:\n\ 166 \ --app-image <file path>\n\ 167 \ Location of the predefined application image that is used\n\ 168 \ to build an installable package\n\ 169 \ (absolute path or relative to the current directory)\n\ 170 \ --file-associations <file path>\n\ 171 \ Path to a Properties file that contains list of key, value pairs\n\ 172 \ (absolute path or relative to the current directory)\n\ 173 \ The keys "extension", "mime-type", "icon", and "description"\n\ 174 \ can be used to describe the association.\n\ 175 \ This option can be used multiple times.\n\ 176 \ --install-dir <file path>\n\ 177 \ {4}\ 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\ 186 \ --runtime-image <file-path>\n\ 187 \ Path of the predefined runtime image to install\n\ 188 \ (absolute path or relative to the current directory)\n\ 189 \ Option is required when creating a runtime package.\n\ 190 \n\ 191 \Platform dependent options for creating the application package:\n\ 192 {3} 193 194 MSG_Help_win_launcher=\ 195 \n\ 196 \Platform dependent option for creating the application launcher:\n\ 197 \ --win-console\n\ 198 \ Creates a console launcher for the application, should be\n\ 199 \ specified for application which requires console interactions\n\ 200 201 MSG_Help_win_install=\ 202 \ --win-dir-chooser\n\ 203 \ Adds a dialog to enable the user to choose a directory in which\n\ 204 \ the product is installed\n\ 205 \ --win-menu\n\ 206 \ Adds the application to the system menu\n\ 207 \ --win-menu-group <menu group name>\n\ 208 \ Start Menu group this application is placed in\n\ 209 \ --win-per-user-install\n\ 210 \ Request to perform an install on a per-user basis\n\ 211 \ --win-shortcut\n\ 212 \ Creates a desktop shortcut for the application\n\ 213 \ --win-upgrade-uuid <id string>\n\ 214 \ UUID associated with upgrades for this package\n\ 215 216 MSG_Help_win_install_dir=\ 217 \Relative sub-path under the default installation location\n\ 218 219 MSG_Help_mac_launcher=\ 220 \ --mac-package-identifier <ID string>\n\ 221 \ An identifier that uniquely identifies the application for macOS\n\ 222 \ Defaults to the main class name.\n\ 223 \ May only use alphanumeric (A-Z,a-z,0-9), hyphen (-),\n\ 224 \ and period (.) characters.\n\ 225 \ --mac-package-name <name string>\n\ 226 \ Name of the application as it appears in the Menu Bar\n\ 227 \ This can be different from the application name.\n\ 228 \ This name must be less than 16 characters long and be suitable for\n\ 229 \ displaying in the menu bar and the application Info window.\n\ 230 \ Defaults to the application name.\n\ 231 \ --mac-package-signing-prefix <prefix string>\n\ 232 \ When signing the application package, this value is prefixed\n\ 233 \ to all components that need to be signed that don't have\n\ 234 \ an existing package identifier.\n\ 235 \ --mac-sign\n\ 236 \ Request that the package be signed\n\ 237 \ --mac-signing-keychain <file path>\n\ 238 \ Path of the keychain to search for the signing identity\n\ 239 \ (absolute path or relative to the current directory).\n\ 240 \ If not specified, the standard keychains are used.\n\ 241 \ --mac-signing-key-user-name <team name>\n\ 242 \ Team name portion in Apple signing identities' names.\n\ 243 \ For example "Developer ID Application: "\n\ 244 245 MSG_Help_linux_install=\ 246 \ --linux-package-name <package name>\n\ 247 \ Name for Linux package, defaults to the application name\n\ 248 \ --linux-deb-maintainer <email address>\n\ 249 \ Maintainer for .deb package\n\ 250 \ --linux-menu-group <menu-group-name>\n\ 251 \ Menu group this application is placed in\n\ 252 \ --linux-package-deps\n\ 253 \ Required packages or capabilities for the application\n\ 254 \ --linux-rpm-license-type <type string>\n\ 255 \ Type of the license ("License: <value>" of the RPM .spec)\n\ 256 \ --linux-app-release <release value>\n\ 257 \ Release value of the RPM <name>.spec file or \n\ 258 \ Debian revision value of the DEB control file.\n\ 259 \ --linux-app-category <category value>\n\ 260 \ Group value of the RPM <name>.spec file or \n\ 261 \ Section value of DEB control file.\n\ 262 \ --linux-shortcut\n\ 263 \ Creates a shortcut for the application\n\ 264 265 MSG_Help_mac_linux_install_dir=\ 266 \Absolute path of the installation directory of the application\n\ 267 268 MSG_Help_default_install_dir=\ 269 \Absolute path of the installation directory of the application on OS X\n\ 270 \ or Linux. Relative sub-path of the installation location of\n\ 271 \ the application such as "Program Files" or "AppData" on Windows.\n\ 272 273 MSG_Help_no_args=Usage: jpackage <options>\n\ 274 \Use jpackage --help (or -h) for a list of possible options\ 275 |