Skip to content
Browse files

8225562: jlink --module-path behavior inconsistent with help/errors

Reviewed-by: alanb
  • Loading branch information
sundararajana committed Dec 9, 2019
1 parent e8496ce commit 0ca9d9a032fc2800cc936799e9ed239076564fda
Showing with 7 additions and 2 deletions.
  1. +7 −2 src/jdk.jlink/share/classes/jdk/tools/jlink/resources/
@@ -38,7 +38,12 @@ main.opt.version=\
\ --version Version information

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

\ --add-modules <mod>[,<mod>...] Root modules to resolve
@@ -115,7 +120,7 @@ err.launcher.main.class.empty:launcher main class name cannot be empty: {0} module name cannot be empty: {0}
err.launcher.value.format:launcher value should be of form <command>=<module>[/<main-class>]: {0} must be specified must be specified is not specified and this runtime image does not contain jmods directory. modules specified to {0}
err.path.not.found=path not found: {0}
err.path.not.valid=invalid path: {0}

0 comments on commit 0ca9d9a

Please sign in to comment.
You can’t perform that action at this time.