< prev index next >

src/jdk.jpackage/share/classes/jdk/jpackage/internal/resources/HelpResources_ja.properties

Print this page




  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-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 modular application image:\n\
  38 \        jpackage create-image -o outputdir -n name \\\n\
  39 \            -m moduleName/className -p modulePath\n\
  40 \        To provide your own options to jlink, run jlink separately:\n\
  41 \            jlink --output app.runtime -m moduleName -p modulePath \\\n\
  42 \                --no-header-files [<additional jlink options>...]\n\
  43 \            jpackage -o outputdir -n name -m moduleName/className \\\n\
  44 \                --runtime-image app-runtime\n\
  45 \    Generate a non-modular application image:\n\
  46 \        jpackage create-image -o outputdir -i inputdir -n name \\\n\
  47 \            --main-class className --main-jar MyJar.jar\n\
  48 \    Generate an application installer:\n\
  49 \        jpackage create-installer -o outputdir -n name \\\n\
  50 \            -m moduleName/className -p modulePath\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\


  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 \  --files -f <input file>[{0}<input file>...]\n\
 115 \          A {0} separated list of files in the input dir to be packaged\n\
 116 \          If omitted, all files in the input directory will be packaged.\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 \n\
 124 \Options for creating the application launcher(s):\n\
 125 \  --add-launcher <file path>\n\
 126 \          Path to a Properties file that contains list of key, value pairs\n\
 127 \          (absolute path or relative to the current directory)\n\
 128 \          The keys "name" (required), "module", "add-modules",\n\
 129 \          "main-jar", "main-class", "arguments", "java-options",\n\
 130 \          "app-version", "icon", and "win-console" can be used.\n\
 131 \          These options are added to, or used to overwrite, the original\n\
 132 \          command line options when building an additional launcher.\n\



 133 \  --arguments <main class arguments>\n\
 134 \          Command line arguments to pass to the main class if no command\n\
 135 \          line arguments are given to the launcher\n\
 136 \  --java-options <java options>\n\
 137 \          Options to pass to the Java runtime\n\
 138 \  --main-class <class name>\n\
 139 \          Qualified name of the application main class to execute\n\
 140 \          This option can only be used if --main-jar is specified.\n\
 141 \  --main-jar <main jar file>\n\
 142 \          The main JAR of the application; containing the main class\n\
 143 \          (specified as a path relative to the input path)\n\
 144 \          Either --module or --main-jar option can be specified but not\n\
 145 \          both.\n\
 146 \  --module -m <module name>[/<main class>]\n\
 147 \          The main module (and optionally main class) of the application\n\
 148 \          This module must be located on the module path.\n\
 149 \          When this option is specified, the main module will be linked\n\
 150 \          in the Java runtime image.  Either --module or --main-jar\n\
 151 \          option can be specified but not both.\n\
 152 {2}\n\
 153 \Options for creating the application installer(s):\n\
 154 \  --app-image <file path>\n\
 155 \          Location of the predefined application image that is used\n\
 156 \          to build an installable package\n\
 157 \          (absolute path or relative to the current directory)\n\
 158 \          See the create-image mode options to create the application image.\n\
 159 \  --file-associations <file path>\n\
 160 \          Path to a Properties file that contains list of key, value pairs\n\
 161 \          (absolute path or relative to the current directory)\n\
 162 \          The keys "extension", "mime-type", "icon", and "description"\n\
 163 \          can be used to describe the association.\n\
 164 \  --identifier <id string>\n\
 165 \          Machine readable identifier of the application\n\
 166 \          The format must be a DNS name in reverse order,\n\
 167 \          such as com.example.myapplication.\n\
 168 \  --install-dir <file path>\n\
 169 \          {4}\
 170 \  --installer-type <type> \n\
 171 \          The type of the installer to create\n\
 172 \          Valid values are: {1} \n\
 173 \          If this option is not specified (in create-installer mode) all\n\
 174 \          supported types of installable packages for the current\n\
 175 \          platform will be created.\n\
 176 \  --license-file <file path>\n\
 177 \          Path to the license file\n\
 178 \          (absolute path or relative to the current directory)\n\




  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 modular application image:\n\
  38 \        jpackage create-app-image -o outputdir -n name \\\n\
  39 \            -p modulePath -m moduleName/className\n\
  40 \        To provide your own options to jlink, run jlink separately:\n\
  41 \            jlink --output appRuntimeImage -p ModulePath -m moduleName\\\n\
  42 \                --no-header-files [<additional jlink options>...]\n\
  43 \            jpackage create-app-image -o outputdir -n name\\\n\
  44 \                -m moduleName/className --runtime-image appRuntimeIMage\n\
  45 \    Generate a non-modular application image:\n\
  46 \        jpackage create-app-image -o outputdir -i inputdir -n name \\\n\
  47 \            --main-class className --main-jar MyJar.jar\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\


  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 \          Machine readable identifier of the application\n\
 168 \          The format must be a DNS name in reverse order,\n\
 169 \          such as com.example.myapplication.\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\


< prev index next >