changeset 57291:153e5f76551d

8225562: jlink --module-path behavior inconsistent with help/errors Reviewed-by: alanb
author sundar
date Mon, 09 Dec 2019 23:00:13 +0530
parents c3203a6a2ed4
children e6ed9bef5f8f
files src/jdk.jlink/share/classes/jdk/tools/jlink/resources/jlink.properties
diffstat 1 files changed, 7 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/src/jdk.jlink/share/classes/jdk/tools/jlink/resources/jlink.properties	Mon Dec 09 19:29:39 2019 +0300
+++ b/src/jdk.jlink/share/classes/jdk/tools/jlink/resources/jlink.properties	Mon Dec 09 23:00:13 2019 +0530
@@ -38,7 +38,12 @@
 \      --version                         Version information
 
 main.opt.module-path=\
-\  -p, --module-path <path>              Module path
+\  -p, --module-path <path>              Module path.\n\
+\                                        If not specified, the JDK's jmods directory\n\
+\                                        will be used, if it exists. If specified,\n\
+\                                        but it does not contain the java.base module,\n\
+\                                        the JDK's jmods directory will be added,\n\
+\                                        if it exists.
 
 main.opt.add-modules=\
 \      --add-modules <mod>[,<mod>...]    Root modules to resolve
@@ -115,7 +120,7 @@
 err.launcher.module.name.empty:launcher module name cannot be empty: {0}
 err.launcher.value.format:launcher value should be of form <command>=<module>[/<main-class>]: {0}
 err.output.must.be.specified:--output must be specified
-err.modulepath.must.be.specified:--module-path must be specified
+err.modulepath.must.be.specified:--module-path is not specified and this runtime image does not contain jmods directory.
 err.mods.must.be.specified:no modules specified to {0}
 err.path.not.found=path not found: {0}
 err.path.not.valid=invalid path: {0}