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 \ This option can be used multiple times.\n\
99 \ --module-path -p <module path>...\n\
100 \ A {0} separated list of paths\n\
101 \ Each path is either a directory of modules or the path to a\n\
102 \ modular jar.\n\
103 \ (each path is absolute or relative to the current directory)\n\
104 \ This option can be used multiple times.\n\
105 \ --runtime-image <file path>\n\
106 \ Path of the predefined runtime image that will be copied into\n\
107 \ the application image\n\
108 \ (absolute path or relative to the current directory)\n\
109 \ If --runtime-image is not specified, jpackage will run jlink to\n\
110 \ create the runtime image using options:\n\
111 \ --strip-debug, --no-header-files, --no-man-pages, and\n\
112 \ --strip-native-commands. --bind-services will also be added if\n\
113 \ --add-modules is not specified.\n\
114 \n\
115 \Options for creating the application image:\n\
116 \ --icon <icon file path>\n\
117 \ Path of the icon of the application package\n\
118 \ (absolute path or relative to the current directory)\n\
119 \ --input -i <input path>\n\
120 \ Path of the input directory that contains the files to be packaged\n\
121 \ (absolute path or relative to the current directory)\n\
122 \ All files in the input directory will be packaged into the\n\
123 \ application image.\n\
124 \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 \ This option can be used multiple times.\n\
99 \ --module-path -p <module path>...\n\
100 \ A {0} separated list of paths\n\
101 \ Each path is either a directory of modules or the path to a\n\
102 \ modular jar.\n\
103 \ (each path is absolute or relative to the current directory)\n\
104 \ This option can be used multiple times.\n\
105 \ --bind-services \n\
106 \ Pass on --bind-services option to jlink (which will link in \n\
107 \ service provider modules and their dependences) \n\
108 \ --runtime-image <file path>\n\
109 \ Path of the predefined runtime image that will be copied into\n\
110 \ the application image\n\
111 \ (absolute path or relative to the current directory)\n\
112 \ If --runtime-image is not specified, jpackage will run jlink to\n\
113 \ create the runtime image using options:\n\
114 \ --strip-debug, --no-header-files, --no-man-pages, and\n\
115 \ --strip-native-commands. --bind-services will also be added if\n\
116 \ --add-modules is not specified.\n\
117 \n\
118 \Options for creating the application image:\n\
119 \ --icon <icon file path>\n\
120 \ Path of the icon of the application package\n\
121 \ (absolute path or relative to the current directory)\n\
122 \ --input -i <input path>\n\
123 \ Path of the input directory that contains the files to be packaged\n\
124 \ (absolute path or relative to the current directory)\n\
125 \ All files in the input directory will be packaged into the\n\
126 \ application image.\n\
127 \n\
|