Unable to derive module descriptor for auto generated module names in Java 9?

by

The solution to this seems to be:-

  • A way possible to uninterruptedly using the same artifact name with a new(different) module name could be by packaging META-INF/MANIFEST.MF of the artifact with an attribute Automatic-Module-Name which governs the name of the module to be used by the module descriptor when converted as an automatic module.

OR

  • Artifact owners can add module declarations using module-info.java to their JAR. (this could result in a slow bottom-up migration)

Since the module declaration defined in the specs as:

A module declaration introduces a module name that can be used in
other module declarations to express relationships between modules. A
module name consists of one or more Java identifiers (§3.8) separated
by “.” tokens.

Intersetingly the declarations suggests –

In some cases, the Internet domain name may not be a valid package
name. Here are some suggested conventions for dealing with these
situations:

  • If the domain name contains a hyphen, or any other special character
    not allowed in an identifier (§3.8), convert it into an underscore.

  • If any of the resulting package name components are keywords (§3.9),
    append an underscore to them.

  • If any of the resulting package name components start with a digit, or
    any other character that is not allowed as an initial character of an
    identifier, have an underscore prefixed to the component.

But keep in mind as you do so that Underscore is a keyword in Java9

enter image description here

int _;  // is would throw an error on javac based out of JDK9
int _native; // works fine

More Related Contents:

  1. List the modules resolved during the application startup
  2. What is an illegal reflective access?
  3. How to solve InaccessibleObjectException (“Unable to make {member} accessible: module {A} does not ‘opens {package}’ to {B}”) on Java 9?
  4. Package conflicts with automatic modules in Java 9
  5. What is an automatic module?
  6. Scanning classpath/modulepath in runtime in Java 9
  7. Is it possible to mix –class-path and –module-path in javac (JDK 9)?
  8. How to use 3rd party library in Java9 module?
  9. How to inject module declaration into JAR?
  10. Accessing resource files from external modules
  11. Create Java runtime image on one platform for another using Jlink
  12. How to hide warning “Illegal reflective access” in java 9 without JVM argument?
  13. Eclipse – module not found when adding module-info.java
  14. Why did Java 9 introduce the JMOD file format?
  15. How do you organize tests in a modular Java project?
  16. What’s the difference between requires and requires static in module declaration
  17. Unable to compile simple Java 10 / Java 11 project with Maven
  18. What is the point of overloaded Convenience Factory Methods for Collections in Java 9
  19. How to express dependency in maven on java ee features for transition to Java 9?
  20. Is there a way to add maven dependencies while using the maven-jlink-plugin?
  21. Tomcat 7.0.73 doesn’t work with java 9
  22. Why is the finalize() method deprecated in Java 9?
  23. Error scanning entry “module-info.class” when starting Jetty server
  24. Java 9: Module java.xml.bind is not accessible in Eclipse
  25. Can Java 9 run on a 32-bit OS?
  26. How to apply Filtering on groupBy in java streams
  27. How to fix the “Found Netty’s native epoll transport in the classpath, but epoll is not available. Using NIO instead” warning?
  28. Declare maven dependency on tools.jar to work on JDK 9
  29. When is “java.io.IOException:Connection reset by peer” thrown?
  30. Stream.peek() method in Java 8 vs Java 9

Leave a Comment