1 MSG_Help_common=Usage: jpackager <mode> <options>\n\

     2 \n\

     3 where mode is one of: \n\

     4 \  create-image\n\

     5 \          Generates a platform-specific application image.\n\

     6 \  create-installer <type>\n\

     7 \          Generates a platform-specific installer for the application.\n\

     8 \          Valid values for "type" are "msi", "rpm", "deb", "dmg", \u201cpkg\u201d,\n\

     9 \          \u201cpkg-app-store\u201d. If "type" is omitted, all supported types of installable\n\

    10 \          packages for current platform will be generated.\n\

    11 \  create-jre-installer <type>\n\

    12 \          Generates a platform-specific installer for Server JRE.\n\

    13 \          Valid values for "type" are "msi", "rpm", "deb", "dmg", \u201cpkg\u201d.\n\

    14 \          If "type" is omitted, all supported types of installable packages\n\

    15 \          for current platform will be generated.\n\

    16 \          \n\

    17 Sample usages:\n\

    18 --------------\n\

    19 jpackager create-image --input inputdir --output outputdir --name AppName --class package.ClassName\n\

    20 or\n\

    21 jpackager create-image -i inputdir -o outputdir -n AppName -c package.ClassName\n\

    22 Generates an application image.\n\

    23 \n\

    24 jpackager create-installer -i inputdir -o outputdir -n "App Name" -c package.ClassName\n\

    25 Generates an application installer.\n\

    26 \n\

    27 jpackager create-jre-installer -n <jre_name> -o outputdir\n\

    28 Generates a Server JRE installer.\n\

    29 \n\

    30 The following options are valid for all platforms:\n\

    31 \  --output -o\n\

    32 \          Name of the directory where generated output file is placed.\n\

    33 \  --input -i\n\

    34 \          Name of the base directory that contains the files to package.\n\

    35 \  --files -f\n\

    36 \          List of files in the base directory. If omitted, all files from "input"\n\

    37 \          directory (which is a mandatory argument in this case) will be packaged.\n\

    38 \  --name -n\n\

    39 \          Name of the application.\n\

    40 \  --main-jar -j\n\

    41 \          The main JAR of the application. This JAR should have the main-class,\n\

    42 \          and is relative to the assembled application directory.\n\

    43 \  --class -c\n\

    44 \          Qualified name of the application class to execute.\n\

    45 \  --version -v\n\

    46 \          Version of the application.\n\

    47 \  --arguments -a\n\

    48 \          Command line arguments to pass to the main class if no arguments\n\

    49 \          are specified by the launcher.\n\

    50 \  --icon\n\

    51 \          Icon of the application bundle.\n\

    52 \  --singleton\n\

    53 \          Prevents multiple instances of the application from launching\n\

    54 \          (see SingleInstanceService API for more details).\n\

    55 \  --identifier\n\

    56 \          Machine readable identifier of the application. The format\n\

    57 \          must be a DNS name in reverse order, such as com.example.myapplication.\n\

    58 \          The identifier is used for composing Single Instance unique id and\n\

    59 \          calculating preferences node to search for User JVM Options\n\

    60 \          (the format is a slash delimited version of the main package name,\n\

    61 \          such as "com/example/myapplication"), see UserJvmOptionsService API\n\

    62 \          for more details.\n\

    63 \  --verbose\n\

    64 \          Enables verbose output.\n\

    65 \  --strip-native-commands\n\

    66 \          Removes native executables from the custom run-time images.\n\

    67 \  --jvm-args\n\

    68 \          JVM flags and options to pass to the application.\n\

    69 \  --user-jvm-args\n\

    70 \          JVM options the user may override along and their default values\n\

    71 \          (see UserJvmOptionsService API for more details).\n\

    72 \  --file-associations\n\

    73 \          Properties file that contains list of key=value parameters that\n\

    74 \          describe a file association. "extension", "mime-type", "icon",\n\

    75 \          "description" can be used as keys for the association.\n\

    76 \  --secondary-launcher\n\

    77 \          Properties file that contains a collection of options for a secondary launcher.\n\

    78 \  --build-root\n\

    79 \          Directory in which to use and place temporary files.\n\

    80 \  --runtime-image\n\

    81 \          Location of the predefined runtime image that is used to build\n\

    82 \          an application image and installable package.

    83 \  --app-image\n\

    84 \          Location of the predefined application image that is used to build\n\

    85 \          an installable package.\n\

    86 \  --install-dir\n\

    87 \          Installation directory of the application. Ignored on Windows, use\n\

    88 \          \u2013-win-dir-chooser to provide an ability to choose an installation directory.\n\

    89 \  --echo-mode\n\

    90 \          Outputs (without executing) native packaging commands so that users\n\

    91 \          can use this as a starting point for addressing more complex needs.\n\

    92 \  --license-file\n\

    93 \          The license file, relative to the base directory.\n\

    94 \  --copyright\n\

    95 \          Copyright for the application.\n\

    96 \  --description\n\

    97 \          Description of the application.\n\

    98 \  --category\n\

    99 \          Category or group of the application.\n\

   100 \  --vendor\n\

   101 \          Vendor of the application.\n\

   102 \n\

   103 Modular options:\n\

   104 \  --module -m\n\

   105 \          Main module of the application. This module must have the main-class,\n\

   106 \          and be on the module path.\n\

   107 \  --module-path -p\n\

   108 \          When packaging the Java Runtime, this is the path JLink looks in for modules.\n\

   109 \  --add-modules\n\

   110 \          List of modules to add to JImage creation, including possible services.\n\

   111 \  --limit-modules\n\

   112 \          Modules to limit JImage creation to.\n\

   113 

   114 MSG_Help_mac=\nThe following options are valid for Mac OS X platforms:\n\

   115 \  --mac-sign\n\

   116 \          Request that the bundle be signed.\n\

   117 \  --mac-bundle-name\n\

   118 \          Name of the application as it appears in the Menu Bar. This can be\n\

   119 \          different from the application name. This name must be less than 16\n\

   120 \          characters long and be suitable for displaying in the menu bar and\n\

   121 \          the application Info window.\n\

   122 \  --mac-bundle-identifier\n\

   123 \          An identifier that uniquely identifies the application for MacOSX\n\

   124 \          (and on the Mac App Store).  May only use alphanumeric (A-Z,a-z,0-9),\n\

   125 \          hyphen (-), and period (.) characters.\n\

   126 \  --mac-app-store-category\n\

   127 \          Mac App Store Categories. Note that the key is the string shown to\n\

   128 \          the user and the value is the ID of the category.\n\

   129 \  --mac-app-store-entitlements\n\

   130 \          File location of a custom mac app store entitlements file.\n\

   131 \  --mac-bundle-signing-prefix\n\

   132 \          When signing the application bundle, this value is prefixed to all\n\

   133 \          components that need to be signed that don't have an existing bundle identifier.\n\

   134 \  --mac-signing-key-user-name\n\

   135 \          User name portion of the typical "Mac Developer ID Application: <user name>" signing key.\n\

   136 \  --mac-signing-keychain\n\

   137 \          Location of the keychain to use. If not specified, the standard keychains are used.\n\

   138 

   139 MSG_Help_linux=\nThe following options are valid for Linux platforms:\n\

   140 \  --linux-bundle-name\n\

   141 \          Name for Linux bundle.\n\

   142 \  --linux-package-deps\n\

   143 \          Required packages or capabilities for the application.\n\

   144 \  --linux-rpm-license-type\n\

   145 \          Type of the license ("License: <value>" of the RPM .spec).\n\

   146 \  --linux-deb-maintainer\n\

   147 \          Maintainer for .deb bundle.\n\

   148 

   149 MSG_Help_win=\nThe following options are valid for Windows platforms:\n\

   150 \  --win-menu\n\

   151 \          Adds the application to the system menu.\n\

   152 \  --win-menu-group\n\

   153 \          Start Menu group this application is placed in.\n\

   154 \  --win-per-user-install\n\

   155 \          Request to perform an install on a per-user basis.\n\

   156 \  --win-dir-chooser\n\

   157 \          Adds a dialog to enable the user to choose a directory in which\n\

   158 \          the product is installed.\n\

   159 \  --win-registry-name\n\

   160 \          Name of the application for registry references. Default is\n\

   161 \          the Application Name with only alphanumerics, dots, and dashes (no whitespace).\n\

   162 \  --win-upgrade-uuid\n\

   163 \          UUID associated with upgrades for this package.\n\

   164 \  --win-shortcut\n\

   165 \          Creates a desktop shortcut for the application.\n\