What’s the difference between requires and requires static in module declaration

by

A requires clause expresses that the required module is needed at compile and run time. Consequently, when the module system encounters such a clause during module resolution (the phase in which module descriptors are processed and dependencies are resolved) it searches the universe of observable modules (the modules in the JDK and on the module path) and throws an error if it doesn’t find the module.

A requires static clause expresses a dependency that is optional at run time. That means at compile time the module system behaves exactly as described above.

At run time, on the other hand, it mostly ignores requires static clauses. If it encounters one, it does not resolve it. That means, if an observable module is only referenced with requires static, it does not make it into the module graph! This can be a little surprising at first. If, on the other hand, the module makes it into the graph in some other way (required by some other module, added manually with --add-modules, drawn in by service binding), all modules that have an optional dependency on it can read it.

More Related Contents:

  1. List the modules resolved during the application startup
  2. How to inject module declaration into JAR?
  3. Replacements for deprecated JPMS modules with Java EE APIs
  4. What is an illegal reflective access?
  5. Unable to derive module descriptor for auto generated module names in Java 9?
  6. How to solve InaccessibleObjectException (“Unable to make {member} accessible: module {A} does not ‘opens {package}’ to {B}”) on Java 9?
  7. Package conflicts with automatic modules in Java 9
  8. JDK9: An illegal reflective access operation has occurred. org.python.core.PySystemState
  9. What is an automatic module?
  10. Scanning classpath/modulepath in runtime in Java 9
  11. How to use 3rd party library in Java9 module?
  12. Error occurred during initialization of boot layer FindException: Module not found
  13. Create Java runtime image on one platform for another using Jlink
  14. Java 9 + maven + junit: does test code need module-info.java of its own and where to put it?
  15. Java 9: Module java.xml.bind is not accessible in Eclipse
  16. Classloaders hierarchy in Java 9
  17. How to extract the file jre-9/lib/modules?
  18. Self-Contained Applications, built in Java
  19. Where do resource files go in a Gradle project that builds a Java 9 module?
  20. Unable to compile simple Java 10 / Java 11 project with Maven
  21. What is the point of overloaded Convenience Factory Methods for Collections in Java 9
  22. Is it possible to mix –class-path and –module-path in javac (JDK 9)?
  23. Observer is deprecated in Java 9. What should we use instead of it?
  24. Is there a way to add maven dependencies while using the maven-jlink-plugin?
  25. Tomcat 7.0.73 doesn’t work with java 9
  26. Why is the finalize() method deprecated in Java 9?
  27. Error scanning entry “module-info.class” when starting Jetty server
  28. How to hide warning “Illegal reflective access” in java 9 without JVM argument?
  29. How do you organize tests in a modular Java project?
  30. Stream.peek() method in Java 8 vs Java 9

Leave a Comment