tkslaw
commented
2 years ago For a reference to how Gradle determines if a dependency is a module or not, see the documentation for the Java Library plugin:
To tell the Java compiler that a Jar is a module, as opposed to a traditional Java library, Gradle needs to place it on the so called module path. It is an alternative to the classpath, which is the traditional way to tell the compiler about compiled dependencies. Gradle will automatically put a Jar of your dependencies on the module path, instead of the classpath, if these three things are true:
java.modularity.inferModulePathis not turned offWe are actually building a module (as opposed to a traditional library) which we expressed by adding the
module-info.javafile. (Another option is to add theAutomatic-Module-NameJar manifest attribute as described further down.)The Jar our module depends on is itself a module, which Gradles decides based on the presence of a
module-info.class— the compiled version of the module descriptor — in the Jar. (Or, alternatively, the presence of anAutomatic-Module-Nameattribute the Jar manifest)
Note the documentation for the Application plugin refers you back to the above documentation.
mkpaz
dlemmermann
Typhon0
Gradle build hits runtime error.
Please see StackOverflow question here for full annotated explanation: https://stackoverflow.com/questions/70137886/why-do-i-get-a-runtime-error-when-trying-to-use-and-run-external-library-animate
In particular please note the discussion in the StackOverflow comments section of the post. Essentially: Gradle only adds dependencies to the module-path if they have a module-info descriptor or if they have an Automatic-Module-Name entry in the manifest file. The AnimateFX library has neither, and so Gradle does not put the dependency on the module-path. I'm not sure if there's a way around this problem while keeping your code modular, which is a need.
System Information