The reason behind this is that meanwhile creating your own class, you had also accepted to create a default class as prescribed by your IDE and after writing your code in your own class, you are getting such an error. In order to eliminate this, go to the PROJECT folder → src → Default package. … Read more
Am I using the new module system correctly? Yes. What you are seeing is intended behavior, and this is because JPMS modules do not allow split packages. In case you are not familiar with the term “split packages” it essentially means two members of the same package coming from two different modules. For example: com.foo.A … Read more
The include directory is for header files, such as jni.h, that are needed when compiling C/C++ code that uses JNI and other native interfaces. It’s nothing to do with jlink. The jlink tool can create a run-time image for another platform (cross targeting). You need to download two JDKs to do this. One for the … Read more
Module: A new language feature introduced in Java 9 (similar to class, interface, package, etc.) that consists of a collection of packages, similar to how a package consists of a collection of types. JAR: An archive file format that bundles code and resources and which can be loaded by the JVM. More specifically, a module … Read more
In order to provide reflective access to your module, Java 9 introduced the open keyword. You can create an open module by using the open keyword in the module declaration. An open module grants reflective access to all of its packages to other modules. For example, if you want to use some framework that heavily … Read more
For a while there were two different opinions on your question but during the development of the module system, the community settled on the reverse DNS approach. Unique Module Names – Reverse DNS Here, the assumption is that module names should be globally unique. Given that goal, the most pragmatic way to get there follows … Read more
It is a single argLine, like: <argLine> –add-exports org.junit.platform.commons/org.junit.platform.commons.util=ALL-UNNAMED –add-exports org.junit.platform.commons/org.junit.platform.commons.logging=ALL-UNNAMED </argLine>
The module system has mainly the following impact on the code: A package can only be accessed from one module (Nested packages are treated as separate, so even though the package java.util is in the module java.base, the package java.util.logging can be in the module java.logging) You can only access public fields and methods of … Read more
One thing I notice is that your application (assuming that it’s packaged in tech.flexpoint.dashman) does not seem to be opened up to Spring in any way, which will surely result in failed class loading/illegal access. I would expect to see something like this in module-info.java (depending on your Spring dependencies): opens tech.flexpoint.dashman to spring.core, spring.beans, … Read more
I first answer your actual question (“What is an automatic module?”), but I also explain what they are there for. It is hard to understand why automatic modules behave the way they do without that information. What is an automatic module? The module system creates a module from every JAR it finds on the module … Read more