Re: Loading groovy as a Jigsaw auto-module

Great! This was a new exception for me. Very good to see that the plugin does its job as expected. cheers, Robert On Sun, 03 Dec 2017 15:31:37 +0100, Ceki Gulcu wrote: Hi Robert, I found running the command mvn

Re: Loading groovy as a Jigsaw auto-module

Hi Robert, I found running the command mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.2:resolve \ -DexcludeTransitive to be highly informative. Thank you. Apparently, there were issues in the way I edited MANIFEST.MF file in groovy-2.4.13.jar. I won't bore you with the

Re: Loading groovy as a Jigsaw auto-module

Please remove my name from your list. Thank you On Sun, Dec 3, 2017 at 09:09 Robert Scholte wrote: > [INFO] --- maven-dependency-plugin:3.0.2:resolve (default-cli) @ > maven-javadoc-plugin --- > [INFO] Can't extract module name from groovy-2.4.13.jar: Provider class >

Re: Loading groovy as a Jigsaw auto-module

[INFO] --- maven-dependency-plugin:3.0.2:resolve (default-cli) @ maven-javadoc-plugin --- [INFO] Can't extract module name from groovy-2.4.13.jar: Provider class groovy not in module Maybe this helps You can confirm this with JShell: String artifact = "" // path to artifact

Re: Loading groovy as a Jigsaw auto-module

On Sun, 03 Dec 2017 13:40:51 +0100, Ceki Gulcu wrote: Hello all, The logback project, more specifically logback-classic, offers the possibility of configuration via a script written in Groovy. Thus, logback-classic has source files written in Java and a few source files in