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 -v\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\

  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\