Fixes #2418.

 * Removed dependency artifacts `org.jline:jline`
 * Added dependency artifacts `org.jline:jline-reader` and `org.jline:jline-console` (`jline-builtins`, `jline-native`, `jline-terminal` and `jline-style` are added transitively)
 * Removed `org.jline` module dependency in module-info.
 * Added `org.jline.reader` and  `org.jline.console` module dependneices to module-info
 * Updated README.md with JPMS info.

Author: brett-smith

dependencies.gradle

@@ -43,7 +43,8 @@ ext {
         springbootstarter : "org.springframework.boot:spring-boot-starter:$springBootVersion",
         springbootannproc : "org.springframework.boot:spring-boot-configuration-processor:$springBootVersion",
         springboottest    : "org.springframework.boot:spring-boot-starter-test:$springBootVersion",
-        jline3            : "org.jline:jline:$jline3Version",
+        jline3reader      : "org.jline:jline-reader:$jline3Version",
+        jline3console     : "org.jline:jline-console:$jline3Version",
         jline2            : "jline:jline:$jline2Version",
         ivy               : "org.apache.ivy:ivy:$ivyVersion",
         compileTesting    : "com.google.testing.compile:compile-testing:$compileTestingVersion",

picocli-shell-jline3/README.md

@@ -59,6 +59,14 @@ The following versions of `jline` and `picocli-shell-jline3` are compatible:
 
 Note: JLine v3.17.1 is not compatible as it is affected by [this bug](https://github.com/jline/jline3/issues/640).
 
+## JPMS Compatibility
+
+Prior to version 4.8.0, using this library in a fully modular application was only possible if you also used the JLine3 bundle module `org.jline`, which is provided by the `org.jline:jline` artifact. If for any reason you were using the individual JLine modules, then this library would be unable to find the `org.jline` module. 
+
+As from version 4.8.0, the reverse is true. If you wish to use this library with a fully modular application, you must use JLines individual component artifacts and cannot use the bundle. Now, `picocli-shell-jline3` depends on the artifacts `org.jline:jline-reader` and `org.jline:jline-console` which provides the `org.jline.reader` and `org.jline.consolle` JPMS modules, will all other dependencies transitvely resolved.
+
+For most people, this change will have little obvious effect. You will still be using `requires transitive info.picocli.shell.jline3` in your `module-info.java`, and you still only need to add `picocli-shell-jline3` to your project. You will only be affected if your application as a whole uses other parts of JLine or 3rd party extensions to it.
+
 See [examples for the older versions](https://github.com/remkop/picocli/wiki/JLine-3-Examples).
 
 ## Demo

picocli-shell-jline3/build.gradle

@@ -14,7 +14,8 @@ java {
 
 dependencies {
     api                rootProject
-    api                supportDependencies.jline3
+    api                supportDependencies.jline3reader
+    api                supportDependencies.jline3console
 }
 
 apply plugin: 'org.beryx.jar' // for compiling module-info on Java 8

picocli-shell-jline3/src/main/java9/module-info.java

@@ -32,7 +32,8 @@
  */
 module info.picocli.shell.jline3 {
     requires info.picocli;
-    requires org.jline;
+    requires transitive org.jline.reader;
+    requires transitive org.jline.console;
 
     exports picocli.shell.jline3;
 }