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", "jvm-args",\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 \  --jvm-args <java vm arguments>\n\
 137 \          Java arguments to pass to the virtual machine\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\

 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\